Automated Pingdom Downtime Alerts
Every few minutes, WebRun opens Pingdom, checks whether any monitored check has gone down, posts an alert to Microsoft Teams the moment it happens naming the check and how long it's been down, and books a calendar reminder for a short post incident review once the check recovers so the cause gets looked at instead of forgotten.
How do I get alerted immediately when a Pingdom check goes down?
WebRun checks Pingdom every few minutes for any monitored check that goes down. It posts an immediate alert to Microsoft Teams naming the check and downtime, and books a short post incident review on the calendar once it recovers, so every real outage gets both a fast alert and a scheduled look at the cause.
- Downtime gets an alert within minutes instead of being noticed by a customer
- Every real incident gets a booked review, not just a fire drill
- Recovery is reported automatically so the team knows when it's over
Built for SRE teams · DevOps · website operations teams · platform teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
my.pingdom.com/loginin a real browser with your saved login - no setup, no API keys. -
1
Pingdom - check for a check that's down
- Open Pingdom and check the status of every monitored check
- Capture the check name and how long it's been down for anything currently down
- Note when a previously down check has recovered
Done when Every check's current status is captured, with any down check flagged.
-
2
Google Calendar - alert the team immediately
WebRun opens Google Calendar to alert the team immediately. - Post an alert to the on call channel the moment a check goes down
- Name the check and how long it's been down
- Post a recovery message once the check is back up
Done when The on call channel has an alert for every check that goes down and recovers.
-
3
Microsoft Teams - book a post incident review
WebRun opens Microsoft Teams to book a post incident review. - Book a short post incident review once a check has recovered
- Add the downtime duration to the event description
- Skip creating a review for a check that recovers within a couple of minutes
Done when A post incident review is booked for every incident lasting more than a couple of minutes.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it restart anything or try to fix the outage?
No. WebRun only reports the downtime. Restarting a service or fixing the outage is always done by your on call engineer.
How fast does the alert go out?
Within a few minutes of the check going down, since Pingdom's status is checked every few minutes.
Why book a review only for longer incidents?
So a two minute blip doesn't clutter the calendar. Anything longer gets a booked slot to actually look at what happened.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.