-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
mountstats collector support NFS RDMA protocol stats #2749
Closed
miloaissatu opened this issue
Jul 18, 2023
· 2 comments
· Fixed by prometheus/procfs#558 · May be fixed by #2825
Closed
mountstats collector support NFS RDMA protocol stats #2749
miloaissatu opened this issue
Jul 18, 2023
· 2 comments
· Fixed by prometheus/procfs#558 · May be fixed by #2825
Labels
Comments
Yeah this seems like something we should support |
@miloaissatu procfs add support nfs rdma protocal parse. prometheus/procfs#558 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Host operating system: output of
uname -a
Linux 5.14.0-162.23.1.el9_1.x86_64 #1 SMP PREEMPT_DYNAMIC Tue Apr 11 19:09:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
node_exporter version: output of
node_exporter --version
node_exporter command line flags
node_exporter log output
Are you running node_exporter in Docker?
No
What did you do that produced an error?
Enable collector.mountstats, system has NFS mounts using RDMA protocol
What did you expect to see?
Node exporter able to parse mountstats for NFS mounts with RDMA protocol
Output of /proc/self/mountstats for a mount
What did you see instead?
mountstats parse error, no detailed nfs mount client stats available
Jul 12 23:51:30 sn3htcw06 node_exporter[2431]: ts=2023-07-12T13:51:30.827Z caller=collector.go:169 level=error msg="collector failed" name=mountstats duration_seconds=0.003460234 err="failed to parse mountstats: invalid NFS protocol \"rdma\" in stats 1.1 statement: [0 0 1093 11 0 442101286 442101259 27 8269562384 1239649 98584262 1057117501 2009661 115761925121512 115760829802743 202123752 57245792 0 4652 0 0 0 0 44440 1157693890 0 78]"
The text was updated successfully, but these errors were encountered: