Are you experiencing a cascade of connected alerts for certain incidents that occur in your system? Our incident grouping feature helps cut through the noise, keeping your team focused on resolving the issue.

Easily consolidate multiple related incidents into a single event by matching key attributes, streamlining collaboration and speeding up resolution.

To enable this functionality, you must first configure grouping in the payload mapping section of your integration, using isGroupingKey attribute key.

Once set up, incidents with matching values for the defined attributes will be grouped.

The screenshot above shows an example for the incident details view of an incident group:

You can view the overall state of the entire incident group. The group remains open until all incidents within it are resolved or until it is manually resolved.
Grouping is determined by the criteria set using isGroupingKey in the incident mapping of the integration. As long as the incident group remains open, any new incidents matching the defined criteria (e.g., attribute UTM = 333) will be added to the group.
You can see all single incidents that are part of the group with their status & attributes.
The history of the incident group. The first incident with a grouping attribute creates the groupt and starts auto-escalations. All collaboration takes part on group level, no seperate alerting for new incidents - this reduces the noise and keeps the focus on resolution. After the group is resolved, the next matching incident will create a new incident group. Exception: When using groupingWindowInSeconds , new incidents that come in during the window will reopen a previously resolved group.

Here's how to set this up via the isGroupingKey in your integration: https://docs.allquiet.app/essentials/inbound#optional%2C-additional-attribute-keys

All Quiet changelog

🆕 Incident Grouping Helps to Reduce Noise