Be smarter about ignoring certain special filesystems about node_exporter HOT 5 CLOSED

👍

from node_exporter.

On my machines, I have noticed the following redundant filesystems:

1. device="none",fstype="selinuxfs",mountpoint="/selinux"
   There is even no such mountpoint shown in "df" output. Something must be related to SELINUX.
2. device="rootfs",fstype="rootfs",mountpoint="/"
   Not sure what it stands for but I have another normal device for mountpoint /, for example:
   device="/dev/mapper/rootvg-rootlv",fstype="ext4",mountpoint="/"

It would be great to have an option to ignore certain fstypes, e.g. fstype!~"rootfs|selinuxfs"

from node_exporter.

rootfs

Is is part of the kernel boot process that's usually mounted over. https://www.kernel.org/doc/Documentation/filesystems/ramfs-rootfs-initramfs.txt explains. It's basically a tmpfs.

Considering all the problems we're seeing with users running the node exporter in Docker, is this something we want to support long term? Doing machine-level monitoring in something designed to provide isolation from the machine seems a bit odd to me.

from node_exporter.

Right now (I'm running the nightly node-exporter nightlies that @brian-brazil provides) this seems to kill all node_filesystem_* stats. I think ignoring errors from statfs calls would be better. Or perhaps making a node_filesystem_statfs_error metric?

from node_exporter.

We're ignoring errors from filesystems now, so this should be mostly okay now.

from node_exporter.