# Monitor host machine using metricbeat system module from inside a metricbeat docker container

**URL:** <https://discuss.elastic.co/t/monitor-host-machine-using-metricbeat-system-module-from-inside-a-metricbeat-docker-container/320420>\
**Category:** Beats\
**Tags:** docker, metricbeat\
**Created:** [December 3, 2022, 11:57pm UTC](https://discuss.elastic.co/t/monitor-host-machine-using-metricbeat-system-module-from-inside-a-metricbeat-docker-container/320420 "2022-12-03T23:57:20Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Anagha\_nambiar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anagha_nambiar/32/97593_2.png) [@Anagha\_nambiar](https://discuss.elastic.co/u/Anagha_nambiar)\
**Post date:** [December 3, 2022, 11:57pm UTC](https://discuss.elastic.co/t/monitor-host-machine-using-metricbeat-system-module-from-inside-a-metricbeat-docker-container/320420/1 "2022-12-03T23:57:20Z")

</div>

We are using metricbeat docker container version 8.1.3 to monitor Linux RHEL machines.  
Used docker-compose file to spin up metricbeat container.

Enabled system module to monitor system metrics.

But we are not able to get the complete filesystem details like mount points and its usage etc.

Suppose if we use the command "df -h", we are finding 15 filesystems. But in kibana it is only showing around 8 filesystems.

I have used a empty value for filesystem ignore in system.yml file. Still it is not showing all the filesystems.

Could you please help on this?

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [December 4, 2022, 12:13am UTC](https://discuss.elastic.co/t/monitor-host-machine-using-metricbeat-system-module-from-inside-a-metricbeat-docker-container/320420/2 "2022-12-04T00:13:55Z")

</div>

Hi @Anagha_nambiar

Perhaps review this [Monitor the host machine](https://www.elastic.co/guide/en/beats/metricbeat/current/running-on-docker.html#monitoring-host)

Particularly #3

> If you want to be able to monitor filesystems from the host by using the [system filesystem metricset](https://www.elastic.co/guide/en/beats/metricbeat/current/metricbeat-metricset-system-filesystem.html), then those filesystems need to be mounted inside of the container. They can be mounted at any location.

with an example

` --mount type=bind,source=/,target=/hostfs,readonly \`

---

<div class="post-metadata">

**Author:** ![Anagha\_nambiar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anagha_nambiar/32/97593_2.png) [@Anagha\_nambiar](https://discuss.elastic.co/u/Anagha_nambiar)\
**Post date:** [December 4, 2022, 12:32am UTC](https://discuss.elastic.co/t/monitor-host-machine-using-metricbeat-system-module-from-inside-a-metricbeat-docker-container/320420/4 "2022-12-04T00:32:12Z")

</div>

Hi @stephenb ,

The issue is resolved now!  
I have provided the mount details in docker-compose file, after which it is showing all the filesystem details now.

Thank you so much!

---

<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:** [January 1, 2023, 2:33am UTC](https://discuss.elastic.co/t/monitor-host-machine-using-metricbeat-system-module-from-inside-a-metricbeat-docker-container/320420/5 "2023-01-01T02:33:11Z")

</div>

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