# Disk Space Metrics "wrong" when working with overlay mounts

**URL:** <https://discuss.elastic.co/t/disk-space-metrics-wrong-when-working-with-overlay-mounts/72442>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [January 23, 2017, 8:18am UTC](https://discuss.elastic.co/t/disk-space-metrics-wrong-when-working-with-overlay-mounts/72442 "2017-01-23T08:18:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![guenther](https://avatars.discourse-cdn.com/v4/letter/g/e36b37/32.png) [@guenther](https://discuss.elastic.co/u/guenther)\
**Post date:** [January 23, 2017, 8:18am UTC](https://discuss.elastic.co/t/disk-space-metrics-wrong-when-working-with-overlay-mounts/72442/1 "2017-01-23T08:18:02Z")

</div>

Hi,

I'm using Metricbeat on a machine where several overlay Filesystems are mounted.  
The hard drive actually only has about 440G but the Kibana Dashboards of Metricbeats show me, that the server has several TeraByte.

Here my `fstab`

```auto
Filesystem Size Used Avail Use% Mounted on
udev 10M 0 10M 0% /dev
tmpfs 51G 402M 50G 1% /run
/dev/md1 440G 341G 77G 82% /
tmpfs 126G 0 126G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 126G 0 126G 0% /sys/fs/cgroup
/dev/md0 488M 60M 403M 13% /boot
overlay 440G 341G 77G 82% /var/lib/docker/overlay2/1d185902cc844e2258b8a2cfae49f87bf16e9de826af54dda94e0cddc46750fa/merged
shm 64M 0 64M 0% /var/lib/docker/containers/ee27506a2ba3ab19d9ac054cf2e2de6e6de4058864ff210259d29fcfcd72bb5b/shm
overlay 440G 341G 77G 82% /var/lib/docker/overlay2/2d4ea2a5fe08d65f4818eea096c59348406aaa24c6bbef2e0bfbae5034714f7d/merged
shm 64M 0 64M 0% /var/lib/docker/containers/e0e8632d6ebdf21b95b8e01b57aae409b29df110b698a10a146d8d826cf14b7d/shm
overlay 440G 341G 77G 82% /var/lib/docker/overlay2/8ebe83c83ac84a35991501e24d2247d64e180b96ce2d7878200280f152b95d09/merged
shm 64M 0 64M 0% /var/lib/docker/containers/53ff1ad89bba276a872d05657119541ace577ea57e74a072a4a392b7a93e4041/shm
overlay 440G 341G 77G 82% /var/lib/docker/overlay2/51285b62ba6e2cf26cb2cb221b5aa6464ed838003aa28b6f5c140dd25c127905/merged
shm 64M 0 64M 0% /var/lib/docker/containers/513f64277184f84db7b7847737f8ce5bf0866d3760dec6304d85e241af9dac63/shm
tmpfs 26G 0 26G 0% /run/user/1901
tmpfs 26G 0 26G 0% /run/user/1001

```

I guess this is due to the overlay Filesystem. Shouldn't they just being ignored?

---

<div class="post-metadata">

**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\
**Post date:** [January 23, 2017, 1:01pm UTC](https://discuss.elastic.co/t/disk-space-metrics-wrong-when-working-with-overlay-mounts/72442/2 "2017-01-23T13:01:18Z")

</div>

We should definitively think about adding an option to filter these out. This also requires that we add the type to the event. Could you open a Feature request for the above on Github and link this thread? [https://github.com/elastic/beats](https://github.com/elastic/beats)

---

<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:** [February 20, 2017, 1:01pm UTC](https://discuss.elastic.co/t/disk-space-metrics-wrong-when-working-with-overlay-mounts/72442/3 "2017-02-20T13:01:31Z")

</div>

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