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
We're considering to use ArgoEvents + ArgoWorkflows for infrastructure automation, especially around incidents management.
Example flow: Alert is triggered -> Argo Source -> Argo workflow to create incident in the system and engage on-calls.
I was looking through available option to deduplicate incoming events and only found an expression based filtering. Consider a scenario where an Alert is triggered multiple time for a single incident. We need to be able to deduplicate such events using a persistence layer. Potential algorithm would look like:
Alert triggered for the first time
Argo source adds unique AlertId to persistence with a given TTL
Alert triggered for the same incident within 10 minutes
Argo source filter out incoming event by querying persistence layer
Let me know if there's a pattern for such flow in Argo events.
Assuming there will be a suggestion to Dedup at source (e.g. Alerting system) I'd question this approach, because there might be different alerting events and systems in our setup and we'd rather offload dedupping to the events system itself.
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
-
Hi there,
Thank you for your product!
We're considering to use ArgoEvents + ArgoWorkflows for infrastructure automation, especially around incidents management.
Example flow: Alert is triggered -> Argo Source -> Argo workflow to create incident in the system and engage on-calls.
I was looking through available option to deduplicate incoming events and only found an expression based filtering. Consider a scenario where an Alert is triggered multiple time for a single incident. We need to be able to deduplicate such events using a persistence layer. Potential algorithm would look like:
Let me know if there's a pattern for such flow in Argo events.
Assuming there will be a suggestion to Dedup at source (e.g. Alerting system) I'd question this approach, because there might be different alerting events and systems in our setup and we'd rather offload dedupping to the events system itself.
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions