prometheus / prometheus/node_exporter

Node exporter complains about unknown metric lines from NFSd on Linux 6.6-rc1

Open
#2,799 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

accepted bug
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

Linux 6.6.0-rc1 vanilla self compiled and running Debian otherwise

node_exporter version: output of node_exporter --version
$ ./node_exporter --version
node_exporter, version 1.6.1 (branch: master, revision: f34aaa61092fe7e3c6618fdb0b0d16a68a291ff7)
  build user:       klausman@felka
  build date:       20230911-15:50:34
  go version:       go1.21.1
  platform:         linux/amd64
  tags:             netgo osusergo static_build
node_exporter command line flags

./node_exporter --web.listen-address=:9101

node_exporter log output

ts=2023-09-11T15:53:30.969Z caller=collector.go:169 level=error msg="collector failed" name=nfsd duration_seconds=0.00018264 err="failed to retrieve nfsd stats: unknown NFSd metric line \"wdeleg_getattr\""

Are you running node_exporter in Docker?

Nope, running in host OS directly.

What did you do that produced an error?

Ran node-exporter as describe above

What did you expect to see?

No errors about unknown metric lines. Not sure if that metric line should actually become a useful exported metric.

What did you see instead?

The log message above

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the nfsd collector named in the error and reproduce the parser failure with Linux 6.6-rc1. Trace how the unknown "wdeleg_getattr" line is handled, then verify the collector no longer reports an unknown-metric error and that the resulting metric behavior matches the intended handling.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, linux
Domain
observability, operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.