Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request to add label for mount point to mountstats #2097

Open
jgauth opened this issue Jul 22, 2021 · 9 comments
Open

Request to add label for mount point to mountstats #2097

jgauth opened this issue Jul 22, 2021 · 9 comments

Comments

@jgauth
Copy link

jgauth commented Jul 22, 2021

Currently the labels for NFS metrics from mountstats are "export", "protocol", "mountaddr"

I'm requesting that another label be added, the mountpoint on the NFS client.

For example if /proc/self/mountstats had the following device info:
device myhostname.com:/exports/example mounted on /auto/example with fstype nfs statvers=1.1

I'd like to have a label: mountpoint: /auto/example, in addition to the label export: myhostname.com:/exports/example

It looks like this is already supported by procfs: https://github.com/prometheus/procfs/blob/master/mountstats.go#L314

@discordianfish
Copy link
Member

Yeah agree, this should have a mountpoint label.

jgauth added a commit to jgauth/node_exporter that referenced this issue Jul 27, 2021
Issue: prometheus#2097
Signed-off-by: John Gauthier <jgauth@users.noreply.github.com>
@SuperQ
Copy link
Member

SuperQ commented Jul 28, 2021

Did we have something like this previously, but removed it to avoid duplicate metrics?

@jgauth
Copy link
Author

jgauth commented Jul 28, 2021

Looks like it: 5a6db5c

Can we include the mountpoint label, while also skipping duplicates?

@SuperQ
Copy link
Member

SuperQ commented Jul 29, 2021

Yea, that seems reasonable. Pick first one, ignore the rest, is that good enough?

@conallob
Copy link
Contributor

I would like to work on this, unless there is already someone actively working on it

@jgauth
Copy link
Author

jgauth commented May 1, 2023

@conallob Please feel free to pick up where I left off - #2102

@dsnt02518
Copy link

By bizarre synchronicity I was actually working on a patch for this before I was aware of this issue. Hopefully the PR above will either resolve this or at least prove helpful.

@conallob
Copy link
Contributor

conallob commented May 2, 2023

I'll take a look at #2102 and try to get a PR out this week

@conallob
Copy link
Contributor

@dsnt02518 Since you have #2676 already open, I'll leave this to you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants