We support automatically creating incidents from ๐Ÿ“Ÿ PagerDuty incidents.

We're working hard on this and plan to support other monitoring tools soon.
Have a specific tool you'd like us to work with? let us know! ๐Ÿ™๐Ÿผ

๐Ÿ›  Setting Up

1๏ธโƒฃ Connect to PagerDuty

2๏ธโƒฃ Enable auto-creation

Navigate to Settings > Integrations > PagerDuty and toggle auto-creation

You can select which PagerDuty services and urgencies you want incidents to be automatically created from. You can choose any combination of services and urgencies that exist in the PagerDuty account you are connected to.

You also select a grouping window. More on that later.

โš™๏ธ How does it work?

Once auto-creation is switched on, incidents will be automatically created in a triage state.
Anyone assigned to the incident in PagerDuty will be pulled into the channel.

When joining a triage incident, you'll be met with this:

๐Ÿ”ฅ A new incident
This will accept this triage incident as a real incident.

  • You will be asked if you'd like to rename the incident, and you'll be able to set any custom fields you have configured

  • All your workflows will kick off once the incident is accepted, and you can get to work

  • The PagerDuty incident which triggered this will become an attachment of your incident.

๐Ÿ”— Part of an existing incident
Was this alert caused by an incident with an existing channel that you already know about?
If so, you can attach the PagerDuty incident to any open incident channel.

The incident that was created in triage will be declined, and the channel will be archived after a short delay.

โŒ Not an incident
Selecting this will decline the incident, and archive the channel.

Declined incidents are excluded from any metrics or workflows that you have set up. It's like they never existed at all.

๐Ÿ‘ฉโ€๐Ÿ‘ฉโ€๐Ÿ‘งโ€๐Ÿ‘ง Grouping Windows

Sometimes multiple PagerDuty incidents trigger in a short space of time, caused by the same underlying problem. To avoid creating unnecessary noise, we recommend configuring a grouping window. This allows us to check in with you before we spin up new incidents automatically.

As an example:

  1. An incident is auto-created from a PagerDuty incident

  2. A second PagerDuty incident is triggered within the grouping window, with a matching service

  3. Instead of creating a new incident, we will post the below message in all open incidents with matching PagerDuty services created within the grouping window.

๐Ÿ”— Part of this incident
This will attach this PagerDuty incident to the existing incident.

  • Any other grouping suggestion messages will be deleted from other channels, it's unlikely it's linked to multiple incidents

  • The incident will be acknowledged in PagerDuty

โŒ Not related to this incident
This will reject the PagerDuty incident from this channel, and remove all references to it.

If the incident is rejected from all incident channels where it was suggested, a new incident will be created in triage and you can take it from there.

What's next?

If you have another monitoring tool (Datadog, Kibana, Sentry etc.) you'd like us to create incidents from, let us know! ๐Ÿ™๐Ÿผ

Did this answer your question?