# Metricbeat/K8s: "error getting group status: open /proc/\<PID\>/cgroup"

**URL:** <https://discuss.elastic.co/t/metricbeat-k8s-error-getting-group-status-open-proc-pid-cgroup/255371>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [November 13, 2020, 6:46pm UTC](https://discuss.elastic.co/t/metricbeat-k8s-error-getting-group-status-open-proc-pid-cgroup/255371 "2020-11-13T18:46:17Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![adrisr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adrisr/32/25423_2.png) [@adrisr](https://discuss.elastic.co/u/adrisr)\
**Post date:** [December 23, 2020, 10:55am UTC](https://discuss.elastic.co/t/metricbeat-k8s-error-getting-group-status-open-proc-pid-cgroup/255371/8 "2020-12-23T10:55:47Z")

</div>

This error is not related to Metricbeat's system module, but to a new feature in [Beats internal monitoring.](https://www.elastic.co/guide/en/beats/metricbeat/current/monitoring.html)

The system module is still understanding the `-system.hostfs` flag and reporting metrics correctly. The only effect of this error is that the internal monitoring metrics from Metricbeat are lacking the new cgroups data.

See this issue for more information: [https://github.com/elastic/beats/issues/23267](https://github.com/elastic/beats/issues/23267)

---

_[View the full topic](https://discuss.elastic.co/t/metricbeat-k8s-error-getting-group-status-open-proc-pid-cgroup/255371)._