For the complete documentation index, see llms.txt. This page is also available as Markdown.

Introduction to escalations

Escalation policies define who gets alerted and when, so incidents don't go unacknowledged.

An escalation policy defines who gets alerted, through which channel, and in what order. When an incident triggers, Spike follows the policy until someone acknowledges or resolves it.

Escalation policies list in Spike
Escalation policies in Spike.

How escalation policies work

Each policy has one or more levels. After Spike sends alerts at the first level, it waits for a configured timeout before moving to the next. If no one acknowledges within that window, the incident escalates to the next level automatically.

You can alert multiple people at the same level, across different channels or the same one. You can configure the timeout between levels and create as many levels as you need.

Escalation policy with two levels in Spike
An escalation policy with two levels and a 5-minute timeout.

Escalations don't repeat automatically. Configure repeat escalations in your integration settings. Learn more

You can create unlimited escalation policies with multiple levels.

Last updated