Skip to main content
When one underlying problem creates several alerts that look almost the same, Auto-group similar alerts nests them under one parent. You still see every alert; they just nest, so the list is not full of duplicates.

​
What grouping looks like

On the parent alert, a Grouped Alerts section lists the children with their severity, status, service, and team. A count badge on the parent (e.g. “3 grouped alerts”) tells you at a glance how big the cluster is. On a child alert, a header at the top says “Grouped under [Parent Name]” with a similarity score badge:
  • 95%+ - red. Near-duplicate.
  • 90 - 95% - amber. Strongly related.
  • Below 90% - blue. Loosely related.

​
Ungrouping

If Warrn grouped two alerts that shouldn’t be together, click Ungroup on the child. The child becomes its own top-level alert again. The parent and other children are untouched. This is reversible: if a future similar alert lands, it can be grouped under the same parent again.

​
When grouping skips

Grouping only fires when:
  • An owner or admin has turned on Auto-group similar alerts under Settings → Incident Policies → Alert noise.
  • A new alert is at least 95% similar to an open alert.
  • Both alerts belong to the same team and service.
Alerts that are too dissimilar, on different services, or arriving when no parent is open stay separate.

​
Matching threshold

The match floor is fixed at 95%. It is deliberately not configurable: automatic parent/child changes should happen only for near-duplicates. Alerts below that floor stay separate and can still appear as related alerts.