# Some cgroup metrics are missing from output

**URL:** <https://discuss.elastic.co/t/some-cgroup-metrics-are-missing-from-output/288524>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [November 5, 2021, 7:44pm UTC](https://discuss.elastic.co/t/some-cgroup-metrics-are-missing-from-output/288524 "2021-11-05T19:44:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vPilot](https://avatars.discourse-cdn.com/v4/letter/v/bbce88/32.png) [@vPilot](https://discuss.elastic.co/u/vPilot)\
**Post date:** [November 5, 2021, 7:44pm UTC](https://discuss.elastic.co/t/some-cgroup-metrics-are-missing-from-output/288524/1 "2021-11-05T19:44:30Z")

</div>

I've got several systems that I have recently started collecting data on via Metricbeat, and am running into an issue on several of them. Particularly, I have a couple of systems that are not reporting back `system.process.cgroup.memory` but I cannot figure out why. I know I've met the criteria for cgroup data to be collected, and I cannot find an immediate OS-level difference between those working and those not working.

Any thoughts on what I can look at next? OS is Ubuntu 18.04 and Metricbeat version is 7.10.1.

---

<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:** [December 3, 2021, 9:44pm UTC](https://discuss.elastic.co/t/some-cgroup-metrics-are-missing-from-output/288524/2 "2021-12-03T21:44:57Z")

</div>

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