prometheus / prometheus/node_exporter

Way to distinguish bind mounted path ?

Open
#600 22 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

accepted enhancement help wanted
Dominant language
Go
Stars
13.8k
Forks
2.7k
Avg merge
1d 23h
Merged PRs (30d)
8

Description

Host operating system:
Linux css 4.4.68-nx #122 SMP Mon May 15 09:46:11 KST 2017 x86_64 GNU/Linux
node_exporter version:
  build user:       root@bb6d0678e7f3
  build date:       20170321-12:12:54
  go version:       go1.7.5
Are you running node_exporter in Docker?

yes

What did you do that produced an error?

With given query below

node_filesystem_size{instance=~"(css).*",fstype=~"(ext4|xfs)",mountpoint!~".*mapper.*",device!~".*mapper.*"}

Result is

node_filesystem_size{device="/dev/sda1",fstype="ext4",instance="css:9100",job="node",mountpoint="/rootfs"}	21003628544
node_filesystem_size{device="/dev/sda3",fstype="ext4",instance="css:9100",job="node",mountpoint="/rootfs/home"}	857421250560
node_filesystem_size{device="/dev/sda3",fstype="ext4",instance="css:9100",job="node",mountpoint="/rootfs/home1"}	857421250560

Actually second record is bind mounted point.
If I can get mount options it would be helpful, to exclude the record.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the node_filesystem_size metric and the filesystem data exposed for the Docker-hosted node_exporter. Investigate how bind-mounted paths are represented in the reported device, filesystem type, and mountpoint labels, and determine whether mount options can distinguish them. Done means the exporter exposes enough information for the bind-mounted record to be excluded reliably.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, go, linux
Domain
observability-sre, operating-systems
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.