Automatically de-duplicate or group similar alerts
The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.
Release notes
Sometimes, all services will alert and create multiple alerts. These alerts aren’t grouped together and you get multiple alerts. Deduplication or grouping of these types of alerts would help here.
Problem to solve
Beyond grouping alerts by the same payload, how can you group similar alerts to avoid alert fatigue.
Intended users
User experience goal
Proposal
Further details
- This was mentioned in the Bi-Monthly Internal Stakeholder Call on 2021-09-02:
We were seeing a problem with duplicate alerts. Sometimes, all services will alert and create multiple alerts. These alerts aren’t grouped together and you get one incident for each alert. Deduplication of these types of alerts would help here.
-
This was also mentioned during the Synchronous test of PagerDuty alerts
📹 Recording link. Igor mentions adding a de-dupe key in the payload to map similar alerts; Pager Duty does something similar, but our internal teams aren't leveraging this atm. -
Consider what Alert Details will look like if Alerts are grouped or de-duped. See @seanarnold's issue for Surface details for different events of an Alert.
-
This topic was also discussed in this thread.
-
This issue on showing the frequency of repeated alerts may also be relevant #322891 (closed).
Permissions and Security
Documentation
Please make updates to the Automatic grouping of identical alerts section of existing documentation.