A common aspect of Opsgenie users don't immediately understand is how Routing Rules, Escalation Policies, and On-Call Schedules work together.
When an alert goes to a team, the first thing it checks is the routing rules on that team to determine where it should go. The Best Practice in this case is to have your routing rules send the alerts to escalation policies, which define who will be notified. Typically the first step in the escalation policy is to notify on-call users in a schedule. Below is an example of how you can setup routing rules to send alerts to different escalations.
Here, you can see that the first routing rule checks to see if the alert has Priority = P1. If it does, it routes it to the "Samir_Critical_Escalation". If it doesn't = P1, it goes on to check if the alert is coming in between 6pm-9am M-F, or on the weekends, if it is then it will be routed to "Samir After Hours Escalation"
If it doesn't match that either, it will be routed to "Samir_NonCritical_Escalation". Each of these escalation policies has different steps in who it will notify, and how long it will wait in between each step. This allows you to escalate high priority alerts more aggressively to ensure that they are being resolved quickly, as compared to non-critical alerts that come in after hours which you might only want to notify someone on-call.
Hope this helps!
When configuring Opsgenie to notify multiple users regarding the same alert, there are a couple of approaches to setting this up effectively. For example, multiple responders can be added on a...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events