# Metricbeat kubernetes module doesn't report container memory

**URL:** <https://discuss.elastic.co/t/metricbeat-kubernetes-module-doesnt-report-container-memory/219381>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [February 14, 2020, 2:12pm UTC](https://discuss.elastic.co/t/metricbeat-kubernetes-module-doesnt-report-container-memory/219381 "2020-02-14T14:12:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![smiklos](https://avatars.discourse-cdn.com/v4/letter/s/e19b73/32.png) [@smiklos](https://discuss.elastic.co/u/smiklos)\
**Post date:** [February 14, 2020, 2:12pm UTC](https://discuss.elastic.co/t/metricbeat-kubernetes-module-doesnt-report-container-memory/219381/1 "2020-02-14T14:12:28Z")

</div>

Hi,

Starting from k8s version 1.14, the kubelet /stats/summary endpoint doesn't return memory info per container but rather per pod only. Looks like metricbeat doesn't handle that and therefor the pre-generated dashboard for k8s (the one using mostly metric-state metrics called [Metricbeat Kubernetes] Overview ECS) shows nothing for memory.

Strange thing is, switching it to `kubernetes.pod.memory.usage.bytes` doesnt work either because it uses the same endpoint and the same container fields even though the pod metrics returned from that endpoint would work perfectly.  
So both the beat logic in data.go (under kubernetes/container) and the dashboard setup seem to be broken.

funny enough, on the documentation they claim that it's tested on v 1.14 but I did check and it doesn't work on any version above 1.13  
[https://www.elastic.co/guide/en/beats/metricbeat/master/metricbeat-module-kubernetes.html](https://www.elastic.co/guide/en/beats/metricbeat/master/metricbeat-module-kubernetes.html)

Anything I'm missing?  
Thanks in advance,

Miklos

---

<div class="post-metadata">

**Author:** ![smiklos](https://avatars.discourse-cdn.com/v4/letter/s/e19b73/32.png) [@smiklos](https://discuss.elastic.co/u/smiklos)\
**Post date:** [February 17, 2020, 7:24am UTC](https://discuss.elastic.co/t/metricbeat-kubernetes-module-doesnt-report-container-memory/219381/2 "2020-02-17T07:24:14Z")

</div>

Corrections:

I'm running on Ubuntu and tested this on microk8s. It turns out that this works when I'm using minikube on kvm. minikube uses docker as runtime while microk8s uses containerd (shouldn't that be the same underneath for docker as well?). So perhaps something with regards to the kubelet metric provider is off when I use microk8s.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 16, 2020, 7:24am UTC](https://discuss.elastic.co/t/metricbeat-kubernetes-module-doesnt-report-container-memory/219381/3 "2020-03-16T07:24:31Z")

</div>

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