Automated StatusCake Outage Postmortem Logging
Every few minutes, WebRun checks StatusCake for monitors reporting downtime, posts a Microsoft Teams alert naming the affected site the moment it happens, and logs the incident window, from the moment it went down to when it recovered, on Google Calendar so the postmortem starts with the facts already gathered.
How do I keep an accurate record of every StatusCake outage for the postmortem?
WebRun checks StatusCake every few minutes for monitors reporting downtime, posting a Microsoft Teams alert the moment one goes down and again when it recovers. It also logs the exact incident window on Google Calendar, so by the time the postmortem happens, the start time, recovery time, and total downtime are already recorded and ready to reference.
- Every outage gets an alert within minutes of happening
- The postmortem starts with accurate timing already logged
- A flapping monitor produces a clear record instead of a confusing single alert
Built for Site reliability engineers · web hosting providers · e-commerce ops teams · IT operations 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
app.statuscake.com/Loginin a real browser with your saved login - no setup, no API keys. -
1
StatusCake - check monitor status
- Open StatusCake and review the status of all monitors
- Identify any monitor that just went down or has since recovered
- Note the downtime start time and, once recovered, the recovery time
Done when Every incident's start and recovery time is identified per monitor.
-
2
Google Calendar - post the downtime alert
calendar.google.com
WebRun opens Google Calendar to log the incident window. - Open the incident log Google Calendar
- Add an event covering the exact incident window once the monitor recovers
- Include the monitor name and total downtime in the event notes
Done when The incident window is logged on the calendar, ready for the postmortem.
-
3
Microsoft Teams - log the incident window
microsoft.com
WebRun opens Microsoft Teams to post the downtime alert. - Post an alert to the engineering Microsoft Teams channel for each new downtime event
- Include the monitor name and the time it went down
- Post a short follow-up when it recovers
Done when The team has a Teams alert for every downtime event and its recovery.
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
Does this replace StatusCake's own alerting?
No. It runs alongside your existing StatusCake alert contacts, adding a Teams post and a logged incident window on top of whatever alerts you already have configured.
Will WebRun write the postmortem itself?
No. It only logs the factual incident window, the start and recovery time. Writing the postmortem analysis and remediation stays with your team.
What if the same monitor flaps up and down repeatedly?
Each down and recovery pair is logged as its own incident window, so a flapping monitor produces a clear record of exactly when each event happened rather than one confusing entry.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.