Run Synthetic Uptime Checks
Every few minutes, WebRun opens each of your monitored URLs, checks the HTTP status and response time against your thresholds, and - if anything fails - raises a PagerDuty incident and posts an alert to Slack before your customers notice.
How can I automatically run synthetic uptime checks and alert my team?
Every few minutes, WebRun hits each of your monitored URLs, checks HTTP status and response time against your thresholds, and - if anything fails - raises a PagerDuty incident and posts an alert to Slack immediately, so your on-call engineer is paged before customers notice an outage.
- Outages detected within minutes without manual monitoring
- On-call engineer paged via PagerDuty before customers report issues
- Response time to incidents cut by eliminating manual checks
Built for DevOps engineers · SRE teams · engineering managers · on-call engineers
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.pagerduty.comin a real browser with your saved login - no setup, no API keys. -
1
Your app - probe each critical endpoint
- Open each monitored URL from your configured list in turn
- Record the HTTP status code and page load time for each
- Compare against your thresholds (e.g. status ≠ 200 or latency > 2 s)
- Collect the list of failing endpoints with their status and response time
Done when Every endpoint has been checked and any failures identified.
-
2
PagerDuty - raise an incident on failure
pagerduty.com
WebRun opens PagerDuty to raise an incident on failure. - Open PagerDuty and navigate to Incidents > Create Incident
- Fill in the affected service, severity, and the failing endpoint details
- Submit the incident so the on-call rotation is paged immediately
Done when A PagerDuty incident is open for every failing endpoint.
-
3
Slack - broadcast the alert to the team
slack.com
WebRun opens Slack to broadcast the alert to the team. - Post a single summary message to your #incidents channel listing each failure
- Include the URL, status code, response time, and a link to the PagerDuty incident
Done when The team has a Slack alert with full failure details and the incident link.
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 page the whole team for a blip?
Only if two consecutive checks fail. A single blip is logged but not escalated, so your on-call engineers aren't woken for transient noise.
How do I add or remove endpoints?
Keep a simple list in your WebRun plan - add or remove URLs there and the next run picks up the change automatically.
Does it resolve incidents automatically when a service recovers?
It flags the recovery in Slack, but leaves the PagerDuty incident for you to resolve - so a human confirms the fix before the book is closed.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.