Configure and manage Escalation Chains
Escalation policies dictate how users and groups are notified when an alert notification is created. They can be very simple, or very complex. You can define as many escalation configurations for an integration as you need, and you can send notifications for certain alerts to a designated place when certain conditions are met, or not met.
Escalation policies have three main parts:
- User settings, where a user sets up their preferred or required notification method.
- An escalation chain, which can have one or more steps that are followed in order when a notification is triggered.
- A route, that allows administrators to manage notifications by flagging expressions in an alert payload.
An escalation chain can have many steps, or only one step. For example, steps can be configured to notify multiple users in some order, notify users that are scheduled for on-call shifts, ping groups in Slack, use outgoing webhooks to integrate with other services, such as JIRA, and do a number of other automated notification tasks.
An escalation workflow can employ routes that administrators can configure to filter alerts by regular expressions in their payloads. Notifications for these alerts can be sent to individuals, or they can make use of a new or existing escalation chain.
Related Oncall resources
Getting started with Grafana OnCall for on-call management
This webinar goes over initial Grafana OnCall configuration, setting up an on-call management process, grouping, alert rendering, and organizing runbooks.
Unified alerting and on-call management in Grafana
In this webinar, we’ll demo the Grafana 8 unified alerting system, and introduce Grafana OnCall, our on-call management tool to resolve incidents faster.
Reducing resolution time (MTTR) with the Grafana Stack: Metrics, logs, tracing, & on-call management
See a live demo of Grafana OnCall, and how to correlate your metrics, logs, and traces to reduce you /MTTR using Grafana’s “single pane of glass” approach.