We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, at my org we are using the infiniband collector in node_exporter .
For our case it's extremely useful to also export an unique identifier like node_guid that can be read from /sys/class/infiniband/<device>/node_guid
node_guid
/sys/class/infiniband/<device>/node_guid
The exporter code heavily relies on the InfiniBandClass contained here, and that identifier is not collected
InfiniBandClass
procfs/sysfs/class_infiniband.go
Lines 121 to 129 in a49c6d2
Is there any design reason for this choic,e or can I just contribute a PR for that ?
The text was updated successfully, but these errors were encountered:
Sounds reasonable, so a PR would be welcome.
Sorry, something went wrong.
Add node_guid to infiniband class (prometheus#665)
f2ff1ec
315af17
6420339
Signed-off-by: Diego Sonaglia <[email protected]>
No branches or pull requests
Hi, at my org we are using the infiniband collector in node_exporter .
For our case it's extremely useful to also export an unique identifier like
node_guid
that can be read from/sys/class/infiniband/<device>/node_guid
The exporter code heavily relies on the
InfiniBandClass
contained here, and that identifier is not collectedprocfs/sysfs/class_infiniband.go
Lines 121 to 129 in a49c6d2
Is there any design reason for this choic,e or can I just contribute a PR for that ?
The text was updated successfully, but these errors were encountered: