prometheus / prometheus/node_exporter
adding mountpoint label in metric if possible
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 13.8k
- Forks
- 2.7k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 8
Description
Host operating system: output of uname -a
4.9.93-010
node_exporter version: output of node_exporter --version
v0.18.0
node_exporter command line flags
Are you running node_exporter in Docker?
Yes
What did you do that produced an error?
What did you expect to see?
we expect the mountpoint labels to be scraped by the export, the mountpoint label was configured via /etc/fstab
LABEL=/home /home ext4 defaults,noatime,nodiratime,nodelalloc,barrier=0 0 0
What did you see instead?
node_filesystem_free_bytes{daemon="node-exporter",device="/dev/sda3",fstype="ext4",grafanak8sapp="true",instance="11.166.79.208:9100",job="node-exporter",kubernetes_namespace="monitoring",kubernetes_pod_name="node-exporter-jcqf9",mountpoint="/",nodename="xxxxxx",pod_template_generation="2"}
--
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the node_exporter filesystem metrics that produce node_filesystem_free_bytes and compare the requested /etc/fstab LABEL value with the current device, fstype, and mountpoint labels. Reproduce the case using the provided /home fstab entry and define whether the expected result is a new filesystem label or a change to the existing mountpoint label.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100