# Metricbeat 5.3.1 not collecting host os process info

**URL:** <https://discuss.elastic.co/t/metricbeat-5-3-1-not-collecting-host-os-process-info/97626>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [August 18, 2017, 6:57pm UTC](https://discuss.elastic.co/t/metricbeat-5-3-1-not-collecting-host-os-process-info/97626 "2017-08-18T18:57:44Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dh2001](https://avatars.discourse-cdn.com/v4/letter/d/c77e96/32.png) [@dh2001](https://discuss.elastic.co/u/dh2001)\
**Post date:** [August 18, 2017, 6:57pm UTC](https://discuss.elastic.co/t/metricbeat-5-3-1-not-collecting-host-os-process-info/97626/1 "2017-08-18T18:57:44Z")

</div>

We have Filebeat and Metricbeat running in a docker container. With  
/proc mounted to /hostfs ro. SLES 12. Using -system.hostfs=/hostfs when running metricbeat. But we do not see any process info for processes in another container. This was working in 5.0.0 before we upgraded to 5.3.1. Did something change?

```auto
metricbeat.modules:

#------------------------------- System Module -------------------------------
- module: system
  metricsets:
    # CPU stats
    - cpu

    # System Load stats
    - load

    # Per CPU core stats
    #- core

    # IO stats
    #- diskio

    # Per filesystem stats
    - filesystem

    # File system summary stats
    #- fsstat

    # Memory stats
    - memory

    # Network stats
    - network

    # Per process stats
    - process
  enabled: true
  period: 30s
  processes: ['.*']
  filters: 
  - drop_event:
     when:
       equals:
         cgroup.memory.mem.limit.bytes: 18446744073709551615

```

---

<div class="post-metadata">

**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\
**Post date:** [August 18, 2017, 9:33pm UTC](https://discuss.elastic.co/t/metricbeat-5-3-1-not-collecting-host-os-process-info/97626/2 "2017-08-18T21:33:45Z")

</div>

Have you looked in the Metricbeat logs for errors or warnings?

Can you try disabling cgroup metrics with `process.cgroups.enabled: false` (for an example see [this](https://www.elastic.co/guide/en/beats/metricbeat/5.3/metricbeat-module-system.html#_module_specific_configuration_notes_7)).

---

<div class="post-metadata">

**Author:** ![dh2001](https://avatars.discourse-cdn.com/v4/letter/d/c77e96/32.png) [@dh2001](https://discuss.elastic.co/u/dh2001)\
**Post date:** [August 21, 2017, 1:59pm UTC](https://discuss.elastic.co/t/metricbeat-5-3-1-not-collecting-host-os-process-info/97626/3 "2017-08-21T13:59:32Z")

</div>

I did look in the logs and there were no errors. I just tried disabling cgroups and it did not make a difference.

We downgraded to 5.2.2 and it works in that release. It seems to stop working in 5.3.

---

<div class="post-metadata">

**Author:** ![dh2001](https://avatars.discourse-cdn.com/v4/letter/d/c77e96/32.png) [@dh2001](https://discuss.elastic.co/u/dh2001)\
**Post date:** [August 30, 2017, 10:04pm UTC](https://discuss.elastic.co/t/metricbeat-5-3-1-not-collecting-host-os-process-info/97626/4 "2017-08-30T22:04:59Z")

</div>

We have Metricbeat and Filebeat running in our own custom docker container. Could the docker metricset changes be causing our problems. I saw there were changes mentioned in the 5.3 release notes.

---

<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:** [September 27, 2017, 10:05pm UTC](https://discuss.elastic.co/t/metricbeat-5-3-1-not-collecting-host-os-process-info/97626/5 "2017-09-27T22:05:22Z")

</div>

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