You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How to create two triggers to monitor success and failure using an Argo Events sensor?
Then the slack sensor's pod log:
{"level":"info","ts":"2025-05-16T05:55:20.153605383Z","logger":"argo-events.sensor","caller":"sensor/trigger_conn.go:271","msg":"trigger conditions not met","sensorName":"workflow-slack-sensor","triggerName":"slack-failed","clientID":"client-4020354806-38","meetDependencies":["succeeded"],"meetEvents":["efa34dd7b3bc42bf88e79f62889a62a4"]}
{"level":"info","ts":"2025-05-16T05:55:20.154719315Z","logger":"argo-events.sensor","caller":"sensor/trigger_conn.go:271","msg":"trigger conditions not met","sensorName":"workflow-slack-sensor","triggerName":"slack-succeeded","clientID":"client-798657282-1","meetDependencies":["succeeded"],"meetEvents":["efa34dd7b3bc42bf88e79f62889a62a4"]}
Both the slack-failed and slack-successed triggers are being triggered after a task successfully finishes. Why is that happening?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Here are event source and sensor:
apiVersion: argoproj.io/v1alpha1 kind: EventSource metadata: name: workflow-events namespace: argo-events spec: template: serviceAccountName: argo resource: workflow-completed-succeeded: namespace: ns1 group: argoproj.io version: v1alpha1 resource: workflows eventTypes: - UPDATE filters: data: - path: body.status.phase type: string value: - Succeeded workflow-completed-failed: namespace: ns1 group: argoproj.io version: v1alpha1 resource: workflows eventTypes: - UPDATE filters: data: - path: body.status.phase type: string value: - Failed --- apiVersion: argoproj.io/v1alpha1 kind: Sensor metadata: name: workflow-slack-sensor namespace: argo-events spec: dependencies: - name: succeeded eventSourceName: workflow-events eventName: workflow-completed-succeeded filters: data: - path: body.status.phase type: string value: - Succeeded - name: failed eventSourceName: workflow-events eventName: workflow-completed-failed filters: data: - path: body.status.phase type: string value: - Failed triggers: - template: name: slack-succeeded slack: slackToken: name: slack-secret key: token channel: general message: | Workflow *{{workflow.name}}* completed successfully!! View: https://argo-workflows.domain/workflows/{{workflow.ns}}/{{workflow.name}} parameters: - src: dependencyName: succeeded dataKey: body.metadata.name dest: workflow.name - src: dependencyName: succeeded dataKey: body.metadata.namespace dest: workflow.ns conditions: slack-succeeded dependencies: ["succeeded"] - template: name: slack-failed slack: slackToken: name: slack-secret key: token channel: general message: | Workflow *{{workflow.name}}* failed!! View: https://argo-workflows.domain/workflows/{{workflow.ns}}/{{workflow.name}} parameters: - src: dependencyName: failed dataKey: body.metadata.name dest: workflow.name - src: dependencyName: failed dataKey: body.metadata.namespace dest: workflow.ns conditions: slack-failed dependencies: ["failed"]I have two questions:
After send message to Slack, the variable didn't been parsed to real event data.
How to parse event metadata correctly?
Then the slack sensor's pod log:
Both the
slack-failedandslack-successedtriggers are being triggered after a task successfully finishes. Why is that happening?Beta Was this translation helpful? Give feedback.
All reactions