Categories: Uncategorized

OnPage: Escalation Policy and Failover

OnPage has a zero tolerance policy when it comes to undelivered messages and alerts, which is why we added Failover Redundancy to our critical alerting platform. Failover Redundancy is, simply put, a part of our Escalation Policy.

What is the OnPage Escalation Policy?

An Escalation Policy makes sure that if an incident is not acknowledged or resolved within a pre-determined amount of time, it will be escalated to the correct user(s). You can customize who you want to receive the alert, the amount of time to wait before escalating to the next user(s), and which user(s) the alert should be escalated to.

fig1: Escalation Policy

When is an escalation policy useful? Imagine that you have an on-call team, monitoring critical systems. In the event of an incident, an alert is sent out either by a fellow team member or one of the monitoring tools connected to the hundreds of end points being monitored. If this alert is not acknowledged, what happens to it?

This is a general scenario in which OnPage is used, especially by our MSP customers. Our Scheduler allows you to schedule on-call teams and allows for precautionary steps to be taken that automate the alert going forth to an escalation team.

Below you will see how one can set an Escalation Interval and Escalation Factor which determines who gets the alert next.

fig2: setting up an Escalation Group

What is a Failover?

In the event a message is sent to an escalation group and does not reach anyone in the escalation group, OnPage offers two new configuration options:

  • Failover To OnPage ID’s: Inform OnPage users (refer to fig1: “Failover OPID(s):”) of the failed message escalation. Failover recipients are sent a modified copy of the original message which includes “FO:” in the subject and the name of the group the message was sent to.
  • Escalation Failover Report: Specify an email address (refer to fig1: “Fail report to email:”) which will receive a report including the message tracking information for the failed escalation. Including the original message subject and body in the report is optional.

fig3: Example of Failover Report

The failover makes sure that the right person is notified when the Escalation Policy does not reach an end user.

Contact OnPage to learn more .

OnPage Corporation

Share
Published by
OnPage Corporation

Recent Posts

OnPage’s Strategic Edge Earns Coveted ‘Challenger’ Spot in 2024 Gartner MQ for Clinical Communication & Collaboration

Gartner’s Magic Quadrant for CC&C recognized OnPage for its practical, purpose-built solutions that streamline critical…

1 day ago

Site Reliability Engineer’s Guide to Black Friday

Site Reliability Engineer’s Guide to Black Friday   It’s gotten to the point where Black Friday…

2 weeks ago

Cloud Engineer – Roles and Responsibilities

Cloud engineers have become a vital part of many organizations – orchestrating cloud services to…

1 month ago

The Vitals Signs: Why Managed IT Services for Healthcare?

Organizations across the globe are seeing rapid growth in the technologies they use every day.…

1 month ago

How Effective are Your Alerting Rules?

How Effective Are Your Alerting Rules? Recently, I came across this Reddit post highlighting the…

2 months ago

Using LLMs for Automated IT Incident Management

What Are Large Language Models?  Large language models are algorithms designed to understand, generate, and…

2 months ago