Fix parts of Grafana dashboards#20
Merged
Merged
Conversation
I think the default scrape interval changed from 15s to 1m, but Grafana defaults to 15s and I guess doesn't query Prometheus for it. This breaks graphs such as CPU usage or network transfer, because they don't have enough data to do a `rate`.
Since it supports hot-reload of config, there's no need for a full restart.
This regenerates the dashboard using the "Export for sharing externally" option, which removes some hard-coded information.
tacaswell
approved these changes
May 11, 2022
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Grafana and Prometheus disagreed on the scraping interval, and this caused some of the
rate-based graphs to show no data. Additionally, I recreated the dashboard in "Export for sharing externally" mode.