Automated Catchpoint Synthetic Test Failure Alerts
Every few minutes, WebRun checks Catchpoint synthetic tests for any that breach their latency or availability threshold, posts a Slack alert with the affected node and test, and sends a Telegram escalation if the same test is still failing 15 minutes later.
How do I get alerted immediately when a Catchpoint synthetic test fails?
WebRun checks Catchpoint synthetic tests every few minutes for threshold breaches, posting a Slack alert with the affected node and test the moment one occurs. If the same test is still breaching 15 minutes later, it sends a Telegram escalation, so a brief blip stays a routine Slack alert while a real outage gets pushed further.
- A threshold breach gets a Slack alert within minutes of happening
- A breach that will not clear gets escalated to Telegram automatically
- Brief blips stay routine instead of paging the whole team
Built for Site reliability teams · network operations teams · digital experience monitoring teams · e-commerce ops
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
portal.catchpoint.comin a real browser with your saved login - no setup, no API keys. -
1
Catchpoint - check synthetic test results
- Open Catchpoint and review synthetic test results across monitored nodes
- Check each test's latency and availability against its configured threshold
- Flag any test currently breaching its threshold and note how long it has been breaching
Done when Every test currently breaching its threshold is identified with its node and duration.
-
2
Slack - post the threshold alert
slack.com
WebRun opens Slack to post the threshold alert. - Post an alert to the monitoring Slack channel for each new threshold breach
- Include the test name, the node, and the current latency or availability figure
- Note whether this is a new breach or one still ongoing
Done when The team has a Slack alert for every current threshold breach.
-
3
Telegram - escalate if it persists
telegram.org
WebRun opens Telegram to escalate if it persists. - Send a Telegram escalation for any test still breaching its threshold after 15 minutes
- Include the test name, node, and total time breaching
- Mark it clearly as an escalation
Done when Any breach still ongoing after 15 minutes has been escalated on Telegram.
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 WebRun change the threshold or the test configuration?
No. It only reads results against the thresholds already set in Catchpoint. Changing a test or its threshold stays a manual action for your team.
Why does it wait 15 minutes before escalating?
So a brief blip does not trigger an unnecessary Telegram escalation. A breach lasting more than 15 minutes usually means it needs more visibility than a routine Slack alert.
Does it cover every monitored node?
Yes, it checks every node and test you have configured in Catchpoint, not just a subset.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.