Modernize Prometheus rules/alerts and Grafana dashboards #404
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Collate upstream rules, alerts, and dashboards and tune for use in Typhoon * Previously, a well-chosen (but older) set of rules, alerts, and dashboards were maintained to reflect metric name changes
dghubble
force-pushed
the
modernize-monitoring
branch
from
c0966bf to
e483c81
Compare
dghubble
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Testing
I've been using this new setup for about 3 weeks. This is a big shift, there is one notable gap (apiserver dash is no longer maintained), but overall I think this provides better monitoring detail and accuracy. Most importantly, these rules/alerts/dashes can better track upstream improvements. Tuning and adjustments will continue.
Alerts should be fairly quiet on bare-metal, GCP, and AWS (i.e. those marked stable).