-
Notifications
You must be signed in to change notification settings - Fork 312
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
procfs still unable to collect IB counters #589
Comments
dswarbrick
added a commit
to dswarbrick/procfs
that referenced
this issue
Feb 15, 2024
This skips parsing /sys/class/infiniband/<device>/ports/<port-num>/counters for irdma devices, which do not expose it, and would previously cause parseInfiniBandPort() to return an error. Instead, irdma devices expose /sys/class/infiniband/<device>/ports/<port-num>/hw_counters. Fixes: prometheus#589 Signed-off-by: Daniel Swarbrick <daniel.swarbrick@gmail.com>
SuperQ
pushed a commit
that referenced
this issue
Feb 15, 2024
This skips parsing /sys/class/infiniband/<device>/ports/<port-num>/counters for irdma devices, which do not expose it, and would previously cause parseInfiniBandPort() to return an error. Instead, irdma devices expose /sys/class/infiniband/<device>/ports/<port-num>/hw_counters. Fixes: #589 Signed-off-by: Daniel Swarbrick <daniel.swarbrick@gmail.com>
jritter
pushed a commit
to jritter/procfs
that referenced
this issue
Jul 15, 2024
This skips parsing /sys/class/infiniband/<device>/ports/<port-num>/counters for irdma devices, which do not expose it, and would previously cause parseInfiniBandPort() to return an error. Instead, irdma devices expose /sys/class/infiniband/<device>/ports/<port-num>/hw_counters. Fixes: prometheus#589 Signed-off-by: Daniel Swarbrick <daniel.swarbrick@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
procfs
is still unable to aid Node Exporter in collecting IB metrics when theirdma
module is loaded but only the cards in use are those using themlx5_0
module.procfs
release (v0.12.0):The text was updated successfully, but these errors were encountered: