[bug] Namespace dashboard shows double resource usage #60
Comments
uhthomas
added a commit
to uhthomas/grafana-dashboards-kubernetes
that referenced
this issue
Jul 24, 2023
… cpu/memory Most queries already use label matcher. The metric reports usage for each individual image, and the whole pod which will result in incorrect reporting if not filtered correctly. Fixes: dotdc#60
uhthomas
added a commit
to uhthomas/grafana-dashboards-kubernetes
that referenced
this issue
Jul 24, 2023
… cpu/memory Most queries already use label matcher. The metric reports usage for each individual image, and the whole pod which will result in incorrect reporting if not filtered correctly. Fixes: dotdc#60
dotdc
pushed a commit
that referenced
this issue
Jul 25, 2023
… cpu/memory Most queries already use label matcher. The metric reports usage for each individual image, and the whole pod which will result in incorrect reporting if not filtered correctly. Fixes: #60
|
🎉 This issue has been resolved in version 1.1.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The cumulative resource usage in the namespace seems to be 1.25 cpu and 2.5Gi (I changed the two graphs to stack), but it appears as 2.5 cpu and 5Gi respectively.
I imagine the queries need the label selector
image!="".How to reproduce?
N/A
Expected behavior
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: