# System integration does not report filesystem metrics for network-mounted filesystem

**URL:** <https://discuss.elastic.co/t/system-integration-does-not-report-filesystem-metrics-for-network-mounted-filesystem/389722>\
**Category:** Elastic Agent\
**Tags:** elastic-stack-monitoring\
**Created:** [August 17, 2026, 2:30pm UTC](https://discuss.elastic.co/t/system-integration-does-not-report-filesystem-metrics-for-network-mounted-filesystem/389722 "2026-08-17T14:30:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Barbarossa](https://avatars.discourse-cdn.com/v4/letter/b/71c47a/32.png) [@Barbarossa](https://discuss.elastic.co/u/Barbarossa)\
**Post date:** [August 17, 2026, 2:30pm UTC](https://discuss.elastic.co/t/system-integration-does-not-report-filesystem-metrics-for-network-mounted-filesystem/389722/1 "2026-08-17T14:30:16Z")

</div>

Hi,

I’m collecting host metrics from my Elasticsearch nodes using the System integration.

Filesystem metrics are collected correctly for all of my local mount points under `/mnt/*`, for example `/mnt/es_data`, but I’m not getting any metrics at all for `/mnt/other_data`.

The only difference I can see is that `/mnt/other_data` is an `nfs4` mount whereas the others are local filesystems.

I’ve already verified that the mount is present and accessible (`findmnt`, `df -T`, `/proc/mounts` and `/proc/self/mountinfo` all show it correctly), but in Kibana, i still do not find anything in `system.filesystem.mount_point` for `/mnt/other_data` data stream directly.

I also checked the System integration configuration in Fleet but couldn’t find anything related to excluding NFS or network filesystems.

Is this expected behaviour for the System integration, or should `nfs4` filesystems be collected as well?

If this is expected, what is the recommended way to collect filesystem metrics for NFS-mounted filesystems? If not, is there something else I should be checking?

Environment:

- Elastic Stack: 9.3.3
- System integration: 2.16.1
- Elastic Agent: 9.3.3 and 8.19.9
- RHEL 9.8

Thanks

---

<div class="post-metadata">

**Author:** ![bmorelli25](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bmorelli25/32/38738_2.png) [@bmorelli25](https://discuss.elastic.co/u/bmorelli25)\
**Post date:** [August 19, 2026, 10:27pm UTC](https://discuss.elastic.co/t/system-integration-does-not-report-filesystem-metrics-for-network-mounted-filesystem/389722/2 "2026-08-19T22:27:29Z")

</div>

Hi Barbarossa. This could be [Metricbeat’s default filtering](https://www.elastic.co/docs/reference/beats/metricbeat/metricbeat-metricset-system-filesystem). When `filesystem.ignore_types` is omitted on Linux, Metricbeat ignores filesystem types marked `nodev` in `/proc/filesystems`, which can include `nfs4`.

In Fleet, can you try to edit the System integration and configure **List of filesystem types to ignore** under both **System filesystem metrics** and **System fsstat metrics** so the rendered Agent policy contains `filesystem.ignore_types: []`?

In other words, are both of these empty?

 ![Screenshot 2026-08-19 at 3.22.39 PM](https://us1.discourse-cdn.com/elastic/original/3X/6/5/65474672cac2e1269753242835d26d3b9ad32410.png)

---

<div class="post-metadata">

**Author:** ![Barbarossa](https://avatars.discourse-cdn.com/v4/letter/b/71c47a/32.png) [@Barbarossa](https://discuss.elastic.co/u/Barbarossa)\
**Post date:** [September 3, 2026, 9:07pm UTC](https://discuss.elastic.co/t/system-integration-does-not-report-filesystem-metrics-for-network-mounted-filesystem/389722/3 "2026-09-03T21:07:15Z")

</div>

Hi,

Thanks for your answer.

I checked this and confirmed that `nfs4` is not configured to be ignored under either the filesystem or fsstat metrics. I also checked the rendered/internal Elastic Agent configuration and couldn’t find anything indicating that `nfs4` is being excluded there.

What makes this more interesting is that the **same Elastic Agent, using the same System integration, is successfully collecting filesystem metrics for another `nfs4` filesystem**. The issue only occurs with this particular network-mounted filesystem.

So my current suspicion is that the problem is related to the way this specific network filesystem is mounted or handled, rather than `nfs4` being excluded in general.

If you have the possibility to reproduce this with a network-mounted NFS filesystem on your side, it would be interesting to know whether you see the same behavior.

In the meantime, I’ve found a workaround for monitoring this filesystem, so from my side this topic can be considered closed for now.

Thanks again for your help!