Incident Status Based Deduplication

Use Incident Status Based Deduplication to deduplicate all open events to an existing open Incident for a service

Incident Status Based Deduplication works on the logic that all incidents that come in for a service is related to the same cause. So, if there is an open (Triggered or Acknowledged state) incident for a service, any and all incidents that come in for this service will get deduplicated against this open incident.

Enabling the Incident Status Based Deduplication

  • You can enable this while adding a service using the Add Service button.

  • Check the box with the information message and choose the appropriate time window for which you'd like this deduplication rule to hold true.

  • By default, this will remain unchecked.

  • If enabled, you will be seeing the Deduplication rule below in the Deduplication UI.

  • You can edit, change the execution priority or delete this rule based on your requirements.

🚧

Note

This option can be enabled only at the start of a Service Creation. If you leave this box unchecked and want to add this as a Deduplication rule later, you can copy paste the rule below and change the execution priority accordingly.

past_incident.is_suppressed == false with the appropriate deduplication time window.

Updated 11 days ago


Incident Status Based Deduplication


Use Incident Status Based Deduplication to deduplicate all open events to an existing open Incident for a service

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.