How to Simulate Alert Escalation and Delays with Simplified Alerting

If you’re currently preparing to migrate your account to our Simplified Alerting System or if you’ve already migrated, and wish to restore some of your alert escalations with delays, here’s a simple and effective hack to simulate the alert escalation and delay features of BeepManager.


If you held a Pingdom account prior to June 2016 - chances are your alerts were handled by our BeepManager Alerting System which supported multiple escalation points and delays like the one pictured below.


We have decided to retire our BeepManager Alerting System because we’re shifting our focus on delivering the best in website availability and performance tools. This effectively means that we’ve removed all escalation alerting points.


We love the beauty in simplicity: enter Pingdom’s new Simplified Alerting System with single endpoint alerting. While it is still possible to CC and alert contacts in an alert policy - you cannot escalate/delay the outgoing alert once your account is migrated.


However, it is possible to simulate the lost escalation with a little bit of sneaky check manipulation.


The first step is to review your current alerting setup. We recommend grabbing screenshots of your alert policies and their connected checks along the way. If you already migrated please skip ahead to the “Duplicate a check” section.


Screen_Shot_2018-02-16_at_13.01.38.pngReview each alert policy - carefully take note of any policies with multiple escalation points.



Next, navigate back to “Alert Policies” and click the “Connect Checks” button.



Next, sort your list of connected checks using the “Connected To” tab. Remember to take a screenshot inc ase you need to reference back.


Armed with your screenshots, your review is complete and you should now have an idea of your active checks, their importance and your alert policies with escalation points - time for migration!

Remember: migrating will delete your escalations points, you cannot reverse this process once completed.


Migration only takes a few minutes and our wizard guides you through the steps for identifying owner endpoints, confirming your alert preferences (email, sms, push), and confirming the importance of your checks.


Duplicating a check - simulating an escalation and delay.


Using your screenshots as a point of reference, add a new duplicate check with a similar alert and delay as your original alert escalation.

Next, navigate to Experience Monitoring > Uptime (new interface).


Next, click the “Add new” button in the upper right corner


Be sure to use a naming convention which makes the duplicated check easy to identify such as “Duplicate2”, and select a similar check interval and test location.


In the same window, simulate the old escalation (refer to your screenshot as needed) and select the person to alert along with a similar delay. In some cases, you’ll need to refer to the old alert policy, adding the first endpoint delay to the escalation delay (i.e. First delay 2 minutes, then escalate after 5 minutes = 7 minutes of total delay).


Once completed, save your new check. Congratulations! You have successfully duplicated your original escalation.


Was this article helpful?
0 out of 0 found this helpful