• Products
  • Get started
  • Documentation
  • Resources

What is alert deduplication?

The feature described in this article is currently rolling out to some Jira Service Management Cloud customers. It may not yet be visible or available on your site.

In complex operational environments, receiving multiple alerts for the same underlying issue can lead to confusion, inefficiency, and can delay resolving the problem. The Deduplication feature addresses this challenge by identifying and consolidating duplicate alerts.

To identify an alert as deduplicated, Jira Service Management analyzes various attributes of incoming alerts, such as source, content, and context, to determine if they are duplicates. The deduplication process reduces the noise and focuses the response efforts on resolving the root cause.

Each deduplication event is logged in the activity log of the deduplicated alert, providing a clear audit trail for tracking and reference.

Alias field

The Alias field in the alert detail is utilized for alert deduplication. The alias serves as a unique identifier for open alerts, allowing for effective identification and consolidation of related alerts. Only one open alert with a specific alias can exist at any given time.

Count property

If a new alert is created with an existing alias, Jira Service Management increments the Count property of the open alert instead of creating a separate alert. You can use the Count property while creating a search syntex. The Count property and logging of deduplication events cease after 100 occurrences, but deduplication continues as long as the alert remains open.

Additional Help