prometheus / prometheus/node_exporter
as a user, i'd like btrfs subvolume metrics
Open
Nobody has claimed this yet.
- 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
➜ uname -a | sed -e "s/${HOST}/HOSTNAME/"
Linux HOSTNAME 6.3.8-arch1-1 #1 SMP PREEMPT_DYNAMIC Wed, 14 Jun 2023 20:10:31 +0000 x86_64 GNU/Linux
node_exporter version: output of node_exporter --version
➜ prometheus-node-exporter --version
node_exporter, version 1.6.0 (branch: tarball, revision: 1.6.0)
build user: someone@builder
build date: 20230530-16:06:09
go version: go1.20.4
platform: linux/amd64
tags: unknown
Currently, the btrfs metrics do not include subvolume utilization information. It would be fantastic if the subvolume ID could be added as a label so that things like showing per-subvolume disk utilization were possible.
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 by locating the existing btrfs collector and its tests, then trace how current btrfs metrics are gathered and exposed. Add coverage for subvolume utilization with the subvolume ID as a label, and verify the resulting per-subvolume metrics against the requested behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux, prometheus
- Domain
- observability, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100