Help
On-Call & Escalation
On-Call at Schedules defines who pages when an alert fires: rotations decide who is on duty now, and escalation policies decide who hears about it next when nobody answers.
Rotations
- A schedule is a named list of members with a hand-off pattern and a start time; the Schedules tab shows who is on call now under the coverage banner, and a schedule's page lists the upcoming hand-offs.
- Overrides cover a swap on the schedule's own page: one member takes another's shift for a window without editing the rotation, and the rotation resumes afterwards.
Escalation policies
- A policy is an ordered list of levels. Each level names its targets (a schedule's on-call member, a fixed member, or everyone holding a role) and a timeout in minutes: how long to give the previous level before escalating.
- Acknowledging an alert stops the chain; it is answered. Resolving an alert stops it too and closes the page.
- Devices and escalation rules route through policies; an alert follows the chain its device or rule names. A level whose targets all vanish still counts as a level, so check the policy's page when a chain should have paged and did not.
See also: Alert Triage for acknowledging and resolving, and Integrations for PagerDuty, Slack and outbound webhooks as level targets.