Argo Events Sensor Quick Fix - Sensor Trigger Configuration

Argo Events sensors listen for events and trigger actions like workflow creation. Misconfigured sensors fail to match events or execute triggers. This guide covers the fix.

Quick Fix

Wrong

apiVersion: argoproj.io/v1alpha1
kind: Sensor
metadata:
  name: github-sensor
spec:
  dependencies:
  - name: webhook-dep
    eventSourceName: webhook
    eventName: example
  triggers:
  - name: trigger-workflow

The issue: trigger has no template specification and no reference to the event in the trigger template. The sensor creates no resources when events arrive.

Right

spec:
  dependencies:
  - name: webhook-dep
    eventSourceName: webhook
    eventName: example
  triggers:
  - name: trigger-workflow
    template:
      name: workflow-trigger
      k8s:
        operation: create
        source:
          resource:
            apiVersion: argoproj.io/v1alpha1
            kind: Workflow
            metadata:
              generateName: triggered-
            spec:
              entrypoint: main
              templates:
              - name: main
                container:
                  image: alpine
                  command: [echo, "triggered"]

# Expected output after applying the fix
# Sensor pod running and listening for events
# On webhook event: Workflow created with generateName
# Trigger execution: Workflow succeeded
# Event dependency resolution: webhook-dep matched

Prevention

• Always define trigger template with operation and source
• Use k8s trigger type for Kubernetes resource creation
• Match eventSourceName and eventName to existing EventSources
• Use generateName in template to avoid name conflicts
• Set operation: create for idempotent trigger actions

DodaTech Tools

Doda Browser's sensor dashboard shows trigger execution history and event matching. DodaZIP archives sensor configurations for audit. Durga Antivirus Pro validates trigger resource templates.

FAQ