Surface details for different events of an Alert
Problem to solve
Triaging alerts in a single interface requires that that tool (GitLab) save and retain the details/payload of the alerts sent to it so that users can load and view different alerts and their attributes in that tool.
Intended Users
Further details
This work supports the direction of the Alert Management product category.
Proposal
Persist detailed alert information in the database once the alert is triggered.
This extends on the data saved by Persist Prometheus alerts in the DB and Persist a Generic Alert information in the DB. This will save each alert events payload, rather than just incrementing a counter.
Permissions and Security
Documentation
Availability & Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
Links / references
backend feature ~"Accepting merge requests" ~"group::health" devopsmonitor Deliverable
This 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.