Escalation Policies

Create a New Escalation Policy   AlertOps has pre-built escalation policies for ease of use, but admins can build their own customized escalation policies as well.   To create a new escalation policy:  Click on Configuration and s...

Pre-Built Escalation Policies  AlertOps comes with pre-built escalation policies to make sending alerts quick and easy. Depending on your package, you may have access to some of these out of the box.  Escalate after 5 minutes if an aler...

The following entitlements are required to make changes to Escalation Policies: Message_Rule_Update - Add and Update existing Escalation Rules Message_Rule_View - View existing Escalation Rules Owner and App Admin user roles have a...

When setting up an Escalation Policy there are two settings for notification delivery: User Settings and Centralized Settings.  In the Rules Tab, toggle the Notify Using setting between centralized or user .   The User setting will es...

Escalation Policies work in conjunction with Schedules to guide alerts, so it's important to include both concepts here. Below are some common use cases that might help when building your own Escalation Policy. Notify One Primary Only This e...

The service-level agreement (SLA) sets an expectation for alerts to be acknowledged measured in hours.  Define an SLA and use Workflows that take action based on SLA targets. Use Reports that track SLA performance to manage your operatio...

In most cases, straightforward interactions with external systems can be handled via Workflows, as is the case with opening and closing most tickets. In other cases, however, admins need to make decisions about tickets after observing the causes of...

In this article, we will explain how to configure an escalation policy that will loop alerts through the notification chain indefinitely until the alert is closed or assigned.  Main Escalation Policy Open the escalation policy upon which you ...