# Metricbeat ZFS capture volume size

**URL:** <https://discuss.elastic.co/t/metricbeat-zfs-capture-volume-size/282012>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [August 19, 2021, 9:26pm UTC](https://discuss.elastic.co/t/metricbeat-zfs-capture-volume-size/282012 "2021-08-19T21:26:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![PublicName](https://avatars.discourse-cdn.com/v4/letter/p/74df32/32.png) [@PublicName](https://discuss.elastic.co/u/PublicName)\
**Post date:** [August 19, 2021, 9:26pm UTC](https://discuss.elastic.co/t/metricbeat-zfs-capture-volume-size/282012/1 "2021-08-19T21:26:10Z")

</div>

After a few hours I've been unable to get Metricbeat to read ZFS stats.

It looks like [GitHub - maireanu/zfsbeat](https://github.com/maireanu/zfsbeat) has gone stale as the last work was 2 years ago.

Seeing as ZFS is nodev in `/proc/filesystems` the default fsstat module in metricbeat is unable to read it. Is their an easy way to see remain space. It would be nice to see the overall health like the above reference but it fails to build.

---

<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 16, 2021, 11:26pm UTC](https://discuss.elastic.co/t/metricbeat-zfs-capture-volume-size/282012/2 "2021-09-16T23:26:59Z")

</div>

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