Hi team, Having an issue with the values of this metric. kubernetes.node.memory.usage.bytes
Looks like is not taking the proper values, for example:
I am using that metric to get the memory usage but is not the correct number, If I compare for example with kubectl command:
Do you have any idea if there is a bug using this field?
Regards!
Looks like all memory size and CPU total are the same for some reason. @ChrsMark Could you double check on this to see if it's a bug please? TIA!!
Hey @Kaiyan_Sheng , yes looks like there is an issue reported in github but not sure if was fixed.
opened 04:52PM - 19 Sep 18 UTC
closed 08:16PM - 17 Apr 21 UTC
docs
Metricbeat
Stalled
needs_team
I was trying to display the memory available vs memory usage of a Kubernetes nod… e but then I noticed something strange. I am not sure whether it's metricsbeat that is at fault or not so I thought I would post it here.
<img width="1810" alt="screen shot 2018-09-19 at 17 47 26" src="https://user-images.githubusercontent.com/6195629/45768238-406ce600-bc34-11e8-9376-6e61ccd697e7.png">
As you can see the `kubernetes.node.memory.usage.bytes` is higher than the `kubernetes.node.memory.allocatable.bytes`. How is that possible?
The unit of measure configured within Grafana (`5.2.3`) is `bytes`. The version of metricbeat is `6.4.0`. The node is a Google Compute Engine instance of type `n1-standard-2 (2 vCPUs, 7.5 GB memory)`.
Regards!
Thanks! What version of Metricbeat are you running?
Hi @Kaiyan_Sheng . We are using 7.12.1 version
system
(system)
Closed
December 22, 2021, 5:54am
6
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.