Aggregate value for kubernetes.container.cpu.request.cores showing 0 even though it isnt

Hello There,

So I used Metricbeat Kubernetes module to push Kubernetes metrics into Elasticsearch and built dashboards on those. As I was creating one specific to kubernetes.container.cpu.request.cores metric, noticed that where ever value for that metric is below 1, it is getting set to 0 and only for values of 1 and above, would it work as expected. Wondering if this is because of wrong type set to that metric or am doing something wrong?Am using ElasticSearch version 6.1

Appreciate your time and inputs on this!!



This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.