sba-ops
commented
2 months ago I'm experiencing the same issues with the helm chart version 62.2.1.
Open jahnavi0912 opened 2 months ago
sba-ops
commented
2 months ago I'm experiencing the same issues with the helm chart version 62.2.1.
Describe the bug a clear and concise description of what the bug is.
We are configuring metrics in Grafana using Prometheus as a data source and facing issues with getting the exact values of Kubernetes node memory usage. We have configured a custom metric in Grafana to fetch the memory usage of nodes in the cluster, but the values do not match when compared with the data obtained directly from the cluster.
We are using the following command to fetch memory and CPU details of nodes in the cluster: oc adm top nodes
The metric we are using in Grafana to fetch the memory status is: node_memory_MemTotal_bytes - node_memory_MemFree_bytes - node_memory_Inactive_file_bytes - node_memory_Buffers_bytes - node_memory_Slab_bytes
Can someone provide a resolution or suggest the correct metric to accurately fetch the memory details of nodes in Grafana?
What's your helm version?
3.14.4
What's your kubectl version?
1.29.2
Which chart?
kube-prometheus-stack
What's the chart version?
61.6.0
What happened?
No response
What you expected to happen?
No response
How to reproduce it?
No response
Enter the changed values of values.yaml?
No response
Enter the command that you execute and failing/misfunctioning.
node_memory_MemTotal_bytes - node_memory_MemFree_bytes - node_memory_Inactive_file_bytes - node_memory_Buffers_bytes - node_memory_Slab_bytes
Anything else we need to know?
No response