In this case, the alert is first routed to a schedule, and then the notification goes to all team members until acknowledgement, ensuring that the Service Level Agreement for P1s is met. Alerts that come in after hours are routed to a specific schedule, and whoever is on call is contacted. The escalation policy shown below is a typical example of how you might choose to route your alerts. Escalation policiesĪn escalation policy determines who, when, and how to notify team members of an open alert or incident. Routing to an on-call schedule means that Opsgenie notifies the person on call when the alert comes through, rather than notifying someone who is on vacation, out sick, or simply not scheduled to work. Using Routing rules, an alert will be routed to the schedule. The rotations are broken out into business hours and after hours. Below, you’ll see an example of a typical schedule. Our flexible tooling allows for daily, weekly, or custom (including follow-the-sun) schedules. Once your team is set up in Opsgenie, the next step is to create an on-call schedule. Here’s how to make the most of Opsgenie’s alerting features: On-call schedules Through the use of on-call schedules, escalations, routing rules, and deep integrations, we empower teams to notify the right people at the right time, while limiting alert fatigue. Opsgenie recognizes that alerting is worthless unless you’re reaching stakeholders who are in a position to help. If your data center is on fire and you alert Karen while she’s vacationing in the Greek Isles, you (and poor Karen) have a problem. But many organizations still struggle to notify the right people at the right time. In the current climate of always-on services, companies need assurance that customers are getting the service they demand and expect – all the time.
For customer-facing SaaS companies, setting up an alerting tool is a no-brainer.
0 kommentar(er)
