node_filesystem_device_error for glusterfs

Host operating system: output of uname -a

Linux nostromo 5.4.0-113-generic #127-Ubuntu SMP Wed May 18 14:30:56 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

node_exporter version: output of node_exporter --version

node_exporter, version 1.3.1 (branch: HEAD, revision: a2321e7b940ddcff26873612bccdf7cd4c42b6b6)
  build user:       root@243aafa5525c
  build date:       20211205-11:09:49
  go version:       go1.17.3
  platform:         linux/amd64

Are you running node_exporter in Docker?

   node-nostromo:
    image: "prom/node-exporter"
    restart: always
    ports:
      - 9100:9100
    volumes:
      - /proc:/host/proc:ro
      - /sys:/host/sys:ro
      - /:/rootfs:ro
      - /var/smartd:/var/smartd:ro
      - /etc/localtime:/etc/localtime:ro
      - /run/systemd/private:/run/systemd/private:ro
      - /var/run/dbus/system_bus_socket:/var/run/dbus/system_bus_socket:ro
    command:
      - '--path.procfs=/host/proc'
      - '--path.sysfs=/host/sys'
      - "--path.rootfs=/rootfs"
      - '--collector.textfile.directory=/var/smartd'
      - '--collector.filesystem.ignored-mount-points'
      - '^/(sys|proc|dev|host|etc|tmpfs|tmps|run|rootfs/run|rootfs/dev|rootfs/var/lib/docker/containers|rootfs/var/lib/docker/overlay2|rootfs/run/docker/netns|rootfs/var/lib/docker/aufs/rootfs/tmp)($$|/)'

What did you do that produced an error?

Exported metric for gluster mountpoints have node_filesystem_device_error

node_filesystem_device_error{device="127.0.0.1:/glusterfs1",fstype="fuse.glusterfs",mountpoint="/datas/glusterfs"} 1

What did you expect to see?

Metrics for the mountpoint, node_filesystem_readonly or node_filesystem_files

What did you see instead?

node_filesystem_device_error only

Start by reproducing the reported node_filesystem_device_error for the glusterfs mount using the supplied node_exporter Docker configuration. Investigate the filesystem metrics path and compare the gluster mount’s available metrics with the expected node_filesystem_readonly or node_filesystem_files output; done means the mount exposes the expected metrics without only reporting device_error.