Skip to main content

Escalation Policies

Define how and when on-call responders are paged.

D
Written by Dave Rochwerger

An escalation policy decides who gets paged, and when, until someone responds. It is a sequence of steps, each with a delay and the people or teams to notify.

๐Ÿ“‹ What a policy shows

  • Name โ€“ what the policy is called.

  • Team โ€“ the team that owns the policy.

  • Steps โ€“ how many steps the policy has.

  • Behavior โ€“ a summary of whether it repeats (for example "Repeats 2 times" or "No repeats") and whether it auto-resolves (for example "Auto-resolves after 4h" or "Never auto-resolves").

โš™๏ธ Actions

  • Add policy โ€“ pick a team and enter a name.

  • Open โ€“ view or edit the policy.

  • Edit โ€“ change the steps, repeat count, and auto-resolve setting.

  • Delete โ€“ remove the policy.

  • Set as default โ€“ make this the team's default policy.

๐Ÿ“Œ How policies work

  • Every team is created with a default policy automatically.

  • A team must have a default policy to be used as a paging target.

  • The repeat count controls how many times the step sequence cycles if no one acknowledges.

  • Auto-resolve, if set, closes the alert after a set number of hours.

  • Policies can be matched by severity, with the default policy catching anything unmatched.

Did this answer your question?