The Outage Incident Agent
This automation monitors a list of public service status pages for outages or incidents and sends a comprehensive report to a designated Slack channel.
Eduardo Rodriguez
Featured Apps
This automation streamlines the process of monitoring the operational status of critical third-party services your business relies on. Here’s how it works:
- Takes Your Input: You provide a list of service status page URLs (like for AWS, GitHub, Stripe, etc.) and a Slack channel for notifications.
- Visits Each Page: The automation uses a cloud browser to navigate to each URL on your list.
- AI-Powered Analysis: For each page, it uses AI to intelligently read and understand the content. It identifies active incidents, such as outages or degraded performance, and is smart enough to distinguish them from scheduled maintenance announcements.
- Builds a Report: It compiles all the findings into a single, easy-to-read summary. The report highlights services with active incidents, lists services that are operating normally, and notes any pages that failed to load.
- Sends to Slack: The final report is sent as a message to your specified Slack channel, giving your team immediate visibility into the health of your critical dependencies.
- "All-Clear" Option: You can configure the automation to send a report even when all services are operational, providing positive confirmation that everything has been checked and is working correctly.
Usage Ideas
- Proactive Incident Response: Monitor your critical vendors (cloud providers, payment gateways, communication tools) and get ahead of issues that could impact your customers.
- Internal Support Empowerment: Give your support team a heads-up on third-party outages so they can provide better, more informed customer service.
- Centralized Status Hub: Create a dedicated Slack channel that acts as a single source of truth for the status of all your key external services.
- IT Operations Awareness: Keep your IT and DevOps teams informed about the stability of tools and platforms they rely on daily, like GitHub, Azure, or Google Cloud.
Customization Ideas
You have significant flexibility to tailor this automation to your specific needs. You can easily:
- Monitor Any Service: Change the list of status pages to monitor any public-facing service that's critical to your operations.
- Choose Your Channel: Direct reports to any Slack channel to ensure the right team members are notified.
- Customize Notifications: Change the look and feel of the Slack report, including the text, emojis, and information included. You can also decide if you want to receive "all-clear" messages when everything is running smoothly.
- Change Notification Platform: While it defaults to Slack, you can have the reports sent to other services, like email or Microsoft Teams.
Agent Inputs
Required Parameters
Name | Type | Default |
|---|---|---|
slackChannel | string | None |
Slack channel to send the incident report to (e.g., #it-incidents) | ||
statusPageUrls | array<string> | [] |
List of status page URLs to monitor (e.g., https://status.aws.amazon.com, https://www.githubstatus.com, https://status.zoom.us) | ||
Optional Parameters
Name | Type | Default |
|---|---|---|
sendWhenAllClear | boolean | true |
Send a report to Slack even when no active incidents are found | ||
