🚨Escalation Policies

Creating an Escalation Policy

You need to provide a name for the policy.

You can provide a comprehensive explanation of the policy, detailing its behavior for your teammates.

This option determines the events upon which an incident starts.

Indicates that a new incident will start when a monitor goes down.

Indicates that a new incident will start when an SSL Certificate's expiry date is close.

Indicates that a new incident will start when a server monitor's rule is triggered.

Indicates that a new incident will start when a cron job's rule is triggered.

If you hover over the information boxes near the trigger events, you can see which monitor types are available for the event.

Configuration of what will happen during the lifespan of an incident.

The icon below indicates the starting point of an incident. It will be used as a reference and build the steps starting from here.

Configuration of when the first step will be executed. The default value is 0, meaning the first step will run as soon as the incident starts.

You could set the incident step's severity when it reaches this step.

Determines which channels you prefer to be notified when the incident reaches this step.

Enabling this option allows you to bypass this behavior and run the step even if the incident is acknowledged.

By default, incidents will stop escalating to the next steps when they're acknowledged by a teammate.

The name and description of the policy is provided here. These are for the identification of the policy.

The recommended approach for the description field is to clarify when notifications will occur and who will receive them.

In this section, you can see all of the Trigger Actions for this policy.

Triggers serve as the defining criteria, outlining the specific events or conditions that, once met, prompt the initiation of an incident.

In the Steps section, the actions that will occur during the lifespan of an incident are listed in a timeline view.

Keep in mind that the wait times are not stacked between steps. Each wait time is relative to the starting point of the incident.

In the Resolve Notifications section, you'll find the list of the notification channels that will receive notifications upon incident resolution.

The monitors that are using this policy are listed here.

This section provides a detailed overview of the Incidents that have been initiated through the utilization of this Escalation Policy.

For comprehensive assistance and guidance on understanding these incidents, we recommend referring to the Understanding the Incidents section.

Last updated 2 months ago