.png)
.png){kind=icon}
.png){kind=icon}
Alert grouping reduces noise and alert fatigue by consolidating related alerts into a single notification. This improves response efficiency, enhances prioritization, simplifies communication, and ultimately leads to faster incident resolution and better overall system reliability.
Alert grouping is especially helpful for organizations with more robust observability stacks that use separate monitors for different aspects of a given service. For exampleβa monitor for error rates, a monitor for latency, a monitor for CPU, and so on, possibly even using multiple monitoring tools as alert sources. When something goes wrong with that particular service, it might trigger several or all related monitors to start sending off alerts. Without automatic alert grouping, itβs up to the responder to identify whether the alerts are related and what to do about them.Β
Using alert grouping means that in this example, the responder only gets paged from the first alert that comes in. Because Rootly is able to identify that the subsequent alerts are related to the initial alert, the responder is not paged for each monitor that gets triggered, but instead sees the additional alerts grouped as Alert Group Members under the original alert (referred to in Rootly as the Alert Group Leader).
β
Grouped alerts are also shown together in a nested view from the Alert index as well:
β
To set up alert grouping, head to Alerts from the left-hand navigation bar in Rootly web, then click the Grouping tab.
Click + New Alert Group and enter a name (required) and a description (optional).
Under Destinations, youβll select the Services, Teams, and/or Escalation Policies youβd like to include in this group.
Under Time Window, specify a time period during which the Alert Group should stay open and accept new alerts. Our default recommendation is 10 minutes.Β
Optionally, you can define additional requirements for the Alert Group under Content Matching by requiring alerts in the group to have the same title, urgency, or any other payload field associated with your alerts.
β
Here's Alex to take you on a video tour of Alert Grouping!
β
π New & Improved
π Added checkbox to have related alerts automatically resolved when incident is canceled. Teams no longer have to manually resolve each related alert when canceling an incident.
π Custom timestamp fields will now align to each userβs preferred timezone setting. Previously, only out-of-box timestamp fields were displayed in the userβs preferred timezone.
π Increased Rootly mobile app push notifications volume on iOS devices to help responders better hear incoming pages.
π Optimized backend logic in fetching incident subscribers to improve overall platform responsiveness.
π Fixed text wrapping issue on web UI for displaying action items that contain long names.
π Alerts details page now refreshes automatically when the status is updated.
π Fixed intermittent issue with action item events failing to trigger workflows.
β
