First look: behind the scenes building an AI incident responder.
First look: behind the scenes building an AI incident responder.
April 9, 2024
Alert sources allow you to ingest alerts from third-party providers and bring them into incident.io - from there, you can set up routes to create incidents and notify your engineers as needed.
Since launching Alerts, we now support over 10 additional alert sources to help you achieve your specific workflows - here’s an overview of some of our most used integrations.
Setting up an email alert source is particularly useful when you want to automate a support issue to incident process. This alert source will allow you to cover complex support use cases, such as the following:
With our Google Cloud alert sources, GCP customers can get alerted for scenarios such as the following:
The Grafana alert source allows you to ingest your Grafana alerts into incident.io. We’ll automatically link you to the Grafana panel that created the alert, shortening the time from firing to resolved by allowing your engineers to jump straight in.
As a bonus, with our AWS SNS integration, we now also support AWS Managed Grafana as a first class integration.
We’ve also released plenty of other alert sources that have their own full set-up instructions. Some of these include:
To get started, head over to Alerts > Sources > New alert source
, and follow the instructions as provided for your chosen provider. You’ll also see a full list of all supported integrations (over 20 and counting!).
If you don’t see your alert source in the list, please send us a message and we’ll be happy to check if it’s possible for us to build an integration with your provider. In the meantime, you can use connect via the generic HTTP alert source to quickly get going.
You can now see both your current and previously edited schedule previews together when making changes to a schedule. This can help you understand the changes you are making and decrease possible mistakes happening when editing.
👷 We’ve improved the performance of external calendar feeds for schedules, which fixes an issue where they sometimes didn’t update
escape
key