-
Type:
Suggestion
-
Resolution: Invalid
-
Component/s: Policies - Notification Policy
-
None
My team uses Opsgenie to route alerts with a variety of priorities. Some of our most frequent alerts are also the low priority ones. Our escalation policy periodically escalates alerts to everyone in the team after a period of inaction by our person on-call, independent of priority.
The low-priority alerts escalating, however, are considered something of a nuisance. My team is exploring options for what to change about our process to meet everyone's needs, and what we really would like is to be able to suppress notifications for only our low priority alerts and only at the time they would escalate from our on-call person to the whole team. (We'd be fine with them staying suppressed forevermore after that, but ideally we want to keep notifying the on-call person of the alert, just not treating them as so urgent as requiring everyone's attention.)
Based on my reading of https://support.atlassian.com/opsgenie/docs/alert-notifications-flow/ it seems like notification policy conditions (by which I mean the predicates like "is this the priority below P3?") are only checked once each time an alert is created; delays don't cause those predicates to be re-checked. It's possible there's a condition based on Actions I've overlooked/don't understand that would enable me to configure what I need. But if so it's not obvious how this should be done.
I would like to ask that we add conditions for notification policies that allow us to apply those notification policies only when determining whether an alert should be escalated, but not on initial alert creation. Doing this would help me suppress notifications at the appropriate time to meet my team's needs.