# Metricbeat don't get all mounting points for filesystems

**URL:** <https://discuss.elastic.co/t/metricbeat-dont-get-all-mounting-points-for-filesystems/259098>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [December 18, 2020, 12:04pm UTC](https://discuss.elastic.co/t/metricbeat-dont-get-all-mounting-points-for-filesystems/259098 "2020-12-18T12:04:46Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vinicius\_Maia](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vinicius_maia/32/41445_2.png) [@Vinicius\_Maia](https://discuss.elastic.co/u/Vinicius_Maia)\
**Post date:** [December 18, 2020, 12:04pm UTC](https://discuss.elastic.co/t/metricbeat-dont-get-all-mounting-points-for-filesystems/259098/1 "2020-12-18T12:04:47Z")

</div>

Hello all,  
I need some help with a problem about my metricbeat setup.  
I'm trying to monitor my elasticsearch server disks with metricbeat.  
In the elasticsearch servers I created a LVM and mounted it in /var/lib/elasticsearch.  
The problem is my metricbeat can't monitor it. It just get the "/" and the "/boot/efi" filesystems.  
I have another server with a LVM mounted in "/work" and in this case, metricbeat can monitor that filesystem.  
I figure out that metricbeat just can't monitor LVMs mounted in some "linux known" directories.  
Please, could someone help me with it?  
Follow my filesystems:

```auto
Filesystem Size Used Avail Use% Mounted on
devtmpfs 7.2G 0 7.2G 0% /dev
tmpfs 7.3G 0 7.3G 0% /dev/shm
tmpfs 7.3G 753M 6.5G 11% /run
tmpfs 7.3G 0 7.3G 0% /sys/fs/cgroup
/dev/sdb3 39G 7.3G 32G 19% /
/dev/sdb1 200M 8.6M 192M 5% /boot/efi
/dev/mapper/vg_elastic-lv_elastic 2.0T 374G 1.6T 20% /var/lib/elasticsearch
10.0.12.71:/elk 8.0E 1.2T 8.0E 1% /data/elk-history
tmpfs 1.5G 0 1.5G 0% /run/user/0
tmpfs 1.5G 0 1.5G 0% /run/user/993
tmpfs 1.5G 0 1.5G 0% /run/user/1000

```

Follow my system.yaml setup:

```auto
- module: system
  period: 10s
  metricsets:
    - cpu
    - load
    - memory
    - network
    - process
    - process_summary
    - socket_summary
    #- entropy
    #- core
    #- diskio
    #- socket
    #- service
    #- users
  process.include_top_n:
    by_cpu: 5 # include top 5 processes by CPU
    by_memory: 5 # include top 5 processes by memory

- module: system
  period: 1m
  metricsets:
    - filesystem
    - fsstat
  processors:
  - drop_event.when.regexp:
      system.filesystem.mount_point: '^/(sys|cgroup|proc|dev|etc|host|lib|snap)($|/)'

- module: system
  period: 15m
  metricsets:
    - uptime

```

---

<div class="post-metadata">

**Author:** ![mtojek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mtojek/32/63863_2.png) [@mtojek](https://discuss.elastic.co/u/mtojek)\
**Post date:** [December 18, 2020, 1:22pm UTC](https://discuss.elastic.co/t/metricbeat-dont-get-all-mounting-points-for-filesystems/259098/2 "2020-12-18T13:22:37Z")

</div>

I wonder if you can find a solution in this thread: [Metricbeat - 'system' -\> 'filesystem' metrics does not include network drives](https://discuss.elastic.co/t/metricbeat-system-filesystem-metrics-does-not-include-network-drives/165420)

---

<div class="post-metadata">

**Author:** ![Vinicius\_Maia](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vinicius_maia/32/41445_2.png) [@Vinicius\_Maia](https://discuss.elastic.co/u/Vinicius_Maia)\
**Post date:** [December 18, 2020, 5:31pm UTC](https://discuss.elastic.co/t/metricbeat-dont-get-all-mounting-points-for-filesystems/259098/3 "2020-12-18T17:31:58Z")

</div>

That discussion helped me to understand some configurations but didn't solve my problem.  
Based on that discussion I made a configuration where I just set the FS type nfs to be ignored:

```auto
Dec 18 12:50:24 vinelk501esf metricbeat: 2020-12-18T12:50:24.148-0300#011INFO#011filesystem/filesystem.go:57#011Ignoring filesystem types: nfs
Dec 18 12:52:33 vinelk501esf metricbeat: 2020-12-18T12:52:33.012-0300#011INFO#011filesystem/filesystem.go:57#011Ignoring filesystem types: nfs
Dec 18 12:52:33 vinelk501esf metricbeat: 2020-12-18T12:52:33.014-0300#011INFO#011filesystem/filesystem.go:57#011Ignoring filesystem types: nfs

```

But metricbeat can't get metrics from my "/dev/mapper/vg\_elastic-lv\_elastic" mounted on "/var/lib/elasticsearch".

I believe the problem is because I didn't mounted the LVM on "/var", but I'm not sure.

I figure it out mounting my "/dev/mapper/vg\_elastic-lv\_elastic" on "/work/elasticsearch".

I'll very happy if someone can help with it.

Regards,  
Vinicius

---

<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 15, 2021, 5:32pm UTC](https://discuss.elastic.co/t/metricbeat-dont-get-all-mounting-points-for-filesystems/259098/4 "2021-01-15T17:32:02Z")

</div>

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