IncidentHub posts related to ops
View All TagsIncidentHub has many integrations to receive alerts. You can choose from Slack, Webhook, Email, Discord, PagerDuty, and more. In this article, we will explore how to receive IncidentHub alerts in your webhooks.
Updated Mar 26, 2025
Staying on top of your third-party Cloud and SaaS service outages is crucial to maintaining the reliability of your own applications. Like many modern teams, Slack might be your communication tool of choice. You can keep up with such incidents by pushing these events to a Slack channel.
IncidentHub has its own Slack app which can be used to push incident lifecycle events to the Slack channel of your choice. It can be used to send incident trigger, update, and resolve events.
You must have the correct permissions on your Slack workspace to be able to do this.
Follow these steps to configure the Slack app in your Slack workspace.
A newer and expanded version of this article is available here.
Last updated on August 8, 2025.
Incident updates on the public status pages of your SaaS vendors and cloud providers are often the first indication that they might have an outage. Providers also post updates about upcoming and ongoing maintenance on their status pages. Monitoring your SaaS and cloud status pages to detect downtime becomes crucial to your business operations. This article will guide you through the process of effectively monitoring such status pages.
There are two ways to monitor multiple status pages:
If you are using the second option, which is the recommended approach, you can skip directly to the section on Use a Status Page Aggregator Tool.
In either case you will need to identify your cloud providers and locate their public status pages first.
Staying on top of your third-party Cloud and SaaS service outages is crucial to maintain the reliability of your own applications. If Discord is your communication tool of choice, you can keep up with such incidents by pushing these events to a Discord channel.
Discord webhooks allow external applications to send messages to specific channels within a Discord server. This article describes how to integrate Discord as a channel in your IncidentHub account using webhooks.
A recent question in an SRE forum triggered this train of thought.
How do I deal with alerts that are triggered by internal patching/release activities but don't actually cause a downtime? If we react to these alerts we might not have time to react to actual alerts that are affecting customers.
I've paraphrased the question to reflect its essence. There is plenty to unravel here.
My first reaction to this question was that the SRE who posted this is in a difficult place with systemic issues.
Without knowing more about the org and their alerting policies, let's look at what we can dig out based on this question alone
A few weeks ago we released a feature on IncidentHub which gives you a historical view of your monitored services' availability.
On the dashboard where you can add services and channels, there is an overview panel that shows total incidents in the last 24 hours. You can get into a more detailed view by clicking on the button next to it. This opens up a popup where you can see active and resolved incidents - in the last 24 hours - and filter them by service.
This panel is good enough for a quick view on what's affecting your dependent services. However, sometimes there is a need to look back further. This is what the Availability page gives you - an overview of service health over the last 30 days.
Let's look at a few examples:
Chances are, most of your third-party cloud and SaaS dependencies are globally distributed and have many regions of operation. Chances are, your applications use a subset of a cloud or SaaS service. If you are monitoring such a service, why should you receive alerts for all regions or every single component in the service?
E.g. if you use Digital Ocean, you might be using Kubernetes in their US locations (NYC and SFO). You would want to know only when there is an outage in one of these locations. Digital Ocean's status page gives you the option to subscribe to outages across the board - it’s all or nothing. This is the case with most services with a few exceptions.
You can now choose which components/regions you wish to monitor in IncidentHub. Let us continue with our Digital Ocean example.
You can choose to monitor all components:
Last updated on August 9, 2025.
PagerDuty's Events API V2 lets you push events from your monitoring systems to PagerDuty. You can send such events when an incident is triggered, updated, or resolved. This article is a short guide on the different options to integrate PagerDuty with your monitoring and alerting systems.
Why should you monitor your third-party Cloud and SaaS vendors if you are in SRE/Ops?
As part of an SRE team, your primary responsibility is ensuring the reliability of your applications. What makes you responsible for monitoring services that you don't even manage? Third-party services are just like yours - with SLAs. And outages happen, affecting you as well as many others who depend on them.
It's a no-brainer that you should know when such outages happen to be on top of things if/when it affects your running applications.
Most of your third party dependencies will have a public status page or a Twitter account where they publish updates on their outages. Here are some seemingly easy ways to monitor these pages
