Automated ThousandEyes Network Outage Alerts
Every few minutes, WebRun checks ThousandEyes for tests reporting a network path outage or a sharp loss spike, saves the path visualization and affected hop to Google Drive, and posts a Slack alert naming the test and the likely affected service, so a network problem gets noticed before users start reporting it.
How do I catch a ThousandEyes network outage before users notice?
WebRun checks ThousandEyes every few minutes for a network path outage or a sharp loss spike, saving the path visualization and affected hop to Google Drive and posting a Slack alert naming the test and likely impacted service. This gets a network problem in front of the team, with evidence attached, before users start reporting it themselves.
- A network outage gets a Slack alert within minutes of starting
- Evidence is preserved automatically for later review or an ISP ticket
- Problems get caught before users start reporting them
Built for Network operations teams · site reliability engineers · IT infrastructure teams · enterprise network 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.thousandeyes.com/loginin a real browser with your saved login - no setup, no API keys. -
1
ThousandEyes - check test results
thousandeyes.com
WebRun opens ThousandEyes to check test results. - Open ThousandEyes and review test results across monitored paths
- Identify any test reporting an outage or a sharp packet loss spike
- Note the affected hop and the service the path supports
Done when Every current network outage or loss spike is identified with its affected hop.
-
2
Google Drive - archive the path visualization
drive.google.com
WebRun opens Google Drive to archive the path visualization. - Open the ThousandEyes Outage Records folder in Google Drive
- Save the path visualization and test detail for each outage
- Name the file with the test name and the date
Done when A saved record exists in Google Drive for every current outage.
-
3
Slack - post the outage alert
slack.com
WebRun opens Slack to post the outage alert. - Post an alert to the network operations Slack channel
- Name the affected test, the likely service impacted, and the affected hop
- Link to the saved Google Drive record
Done when The team has a Slack alert for every current network outage.
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 reroute traffic or contact the ISP?
No. It only detects the outage, saves the evidence, and alerts the team. Rerouting traffic or opening a ticket with a provider stays with your network operations team.
What counts as an outage worth alerting on?
A test reporting a full path outage or a packet loss spike well above its normal baseline, so routine minor jitter does not trigger an alert.
Why save the visualization to Drive as well as posting to Slack?
The saved record preserves the exact path detail at the time of the outage, which is useful evidence when following up with an ISP or reviewing the incident later.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.