change sum_rate to sum_irate in dashboards and prometheusrules #744
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.
What
After deploying the monitoring stack I notices a number of panels with no data
This may be due to me using the latest version of grafana and prometheus in Operatorhub
found a lot of the queries that failed were using
node_namespace_pod_container:container_cpu_usage_seconds_total:sum_rate
found they panels work again if switched to
node_namespace_pod_container:container_cpu_usage_seconds_total:sum_irate
And found an issue regarding this change regarding a breaking change from rate to irate
kubernetes-monitoring/kubernetes-mixin#670
Guessing this can't merge because of the older versions of prometheus and grafana don't support it.