This message was deleted.
# support
s
This message was deleted.
👀 1
s
What is the query? Or do you use some existing dashboard? We use these ourselves and they are correct https://github.com/SigNoz/dashboards/tree/main/k8s-infra-metrics.
e
this is just great.. Thank you for sharing this as I can see now what was wrong with my settings. while I was using
k8s_node_memory_usage
it looks like what I was looking for is
k8s_node_memory_working_set
also instead of
k8s_node_memory_available
i should have used
k8s_node_allocatable_memory
Is there any valid documentation to describe the meaning of each metric?
same goes for
k8s_node_cpu_utilization
why isnt that metric represents the used_cpu/allocatable_cpu?
e
Thanks for you help! I'll look into it
I can see now some explanation about CPU, but still cant make sense out of this
s
Which part is not clear?
e
what is usage an what is working set for example I would assume that usage is what i will get performing
kubectl top nodes
s
Usage is total memory used (this includes the cache such as page cache etc...); Some part of this memory can be evicted when the kernel gets a request from another process for memory. The working set is the amount of memory required for the process to run. working <= usage.
e
thanks for this detailed explanation
100 Views