# Aggregate value for kubernetes.container.cpu.request.cores showing 0 even though it isnt **URL:** \ **Category:** Elasticsearch\ **Created:** [March 7, 2019, 10:56pm UTC](https://discuss.elastic.co/t/aggregate-value-for-kubernetes-container-cpu-request-cores-showing-0-even-though-it-isnt/171393 "2019-03-07T22:56:55Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Vishnu59](https://avatars.discourse-cdn.com/v4/letter/v/8c91f0/32.png) [@Vishnu59](https://discuss.elastic.co/u/Vishnu59)\ **Post date:** [March 7, 2019, 10:56pm UTC](https://discuss.elastic.co/t/aggregate-value-for-kubernetes-container-cpu-request-cores-showing-0-even-though-it-isnt/171393/1 "2019-03-07T22:56:55Z")
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 ![image](https://us1.discourse-cdn.com/elastic/original/3X/e/4/e4512fd439cb573f89942eff24a25a32883e4ad9.png) ![image](https://us1.discourse-cdn.com/elastic/original/3X/f/6/f6358beba8bdacd450d1514d72843162437bc282.png) Appreciate your time and inputs on this!! Thanks, CK ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 4, 2019, 10:57pm UTC](https://discuss.elastic.co/t/aggregate-value-for-kubernetes-container-cpu-request-cores-showing-0-even-though-it-isnt/171393/2 "2019-04-04T22:57:01Z")
Closed on April 4, 2019, 10:57pm UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.