You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Does anybody know if it's possible to avoid new automatic alert creation when an incident is created from an alert. Is mandatory to get 2 new alerts or are we missing something? Seems to be quite redundant
The process is as follows:
Hi @Pedro Parellada ,
That's the current workflow with Opsgenie incidents.
Say for example an incident is created automatically through an incident rule, and the incident rule is tied to a service:
The service adds multiple responders to the incident at creation:
The alert that initially created the incident would become an Associated alert - and doesn't notify anyone.
The incident then creates a Responder alert for each responder added by the service, and does notify each responder:
The idea behind this workflow is that each responder might have a different configuration in which they need to be notified when an incident triggers; each team could have different routing rules or escalations that manage incidents vs. alerts, each user might have different notifications rules for incidents vs. alerts, etc.
Hope that helps make sense of why two (or more) alerts are created for an incident. And unfortunately at this time there isn't a way to disable this workflow.