New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refacto: write more accurate descriptions for faster troubleshooting #85
Comments
We can probably find a balance between:
Gitlab infrastructure team adds a reference to a troubleshooting markdown. See: |
This is what alert name should be about as this is the first thing operator sees when receives alert. Additionally, this could be enhanced by
In prometheus community this is usually done with either
This is basically a runbook/SOP. For example kubernetes-mixin project includes those as Such runbooks are located in one file, and links are made to specific anchors. This field is usually the most problematic one, as creating a runbook needs a deep knowledge of the system itself. Essentially those are problems already solved by the prometheus community. |
Example:
From:
To:
An
effect
field would enable us to improve alert template.The text was updated successfully, but these errors were encountered: