Render runbooks in alerts
Problem to solve
When an incident occurs, knowing how to respond can be difficult, especially if on-call engineers are not the individuals who wrote the code causing an incident. Having access to runbooks or knowledge about a metric causing alerts is critical to solving a problem and identifying the root cause cause quickly. Ideally, runbooks should be very accessible during a firefight.
Intended users
User experience goal
Users can immediately access the correct runbook in alerts via a resource tab.
Proposal
Render runbooks in GitLab alerts. Begin by supporting Runbooks formatted in wikis. Future iterations will involve integrations with GitLab Runbooks and perhaps other external formats.
Further details
This work supports the Incident Management direction.
Permissions and Security
Documentation
Availability & Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Premium tier - Director level.
Runbooks are leveraged by teams of multiple responders. They are prepared based on experience, knowledge, and collaboration. The purpose is to enable whomever is on-call regardless of skill or experience, to quickly solve a problem.
Is this a cross-stage feature?
Links / references
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.