Incident data available in alerts
As a user, I want to be proactively informed about incidents with meaningful information.
Idea: Add incident automation data (incident title, description and severity) as expansion variables to alerts, so that they can be used in alert payloads.
Log in to comment and vote
Comments5
Hervé Labas
Jul 20
Hi Simon!
I’m afraid I might not have fully understood what you’re trying to achieve exactly.
Incident automation being about creating an incident after an alert, I wonder how you’re intending to use the incident information as part of the alert itself.
Would that be to be aware at alert-level that the alert will trigger an incident?
Simon B.
Jul 20
Ok I was afraid getting that reply :)
I think what I’m trying to achieve is to send notifications to a teams channel for incidents instead alerts, including incident updates and resolutions.
Notification payload should include incident title, description, severity and the duration in the resolution event. That’s what our non-tech teams really care about.
I was hoping that there would be a quickwin using the alerting feature ;)
Hervé Labas
Jul 20
Would a feature that allows for incidents to be subscribed via webhooks open the option to implement some custom routing to an MS Teams channel by any chance?
We’re considering adding support for supporting webhooks as a subscription channel for incidents, and I suppose this could help.
I’d love to know if that’s the case!
Simon B.
Jul 21
I guess it would, although that’ll require an intermediate layer. Not the end of the world, but also not ideal.
Btw, I’m moving from StatusPal, where they have out of the box support to send notifications to a teams webhook. Having said that, I prefer the checkly approach with the ability to customize the template.
Hervé Labas
Jul 22
Thanks for the additional details. We’ll keep you posted on these.
We’re currently looking at somewhere end of Q3 / during Q4 for webhooks support for incident subscriptions depending on how things go.