prometheus / prometheus/node_exporter

node_exporter collector failure for zfs err="couldn't get sysctl: no such file or directory"

Open
#2,847 6 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

FreeBSD stable/14-n265566 aarch64 1400500 1400500

node_exporter version: output of node_exporter --version

% node_exporter --version
node_exporter, version (branch: , revision: unknown)
build user:
build date:
go version: go1.20.8
platform: freebsd/arm64
tags: unknown

node_exporter command line flags

(defaults)

node_exporter log output

Nov 15 17:14:22 REDACTED node_exporter[58452]: ts=2023-11-15T17:14:22.737Z caller=collector.go:169 level=error msg="collector failed" name=zfs duration_seconds=0.000465773 err="couldn't get sysctl: no such file or directory"

(every 15 seconds in /var/log/daemon.log)

Workaround for now is editing /usr/local/etc/rc.d/node_exporter and finding this line:

: ${node_exporter_args:=""

and editing it like so:

: ${node_exporter_args:="--no-collector.zfs"}
then restarting node_collector.

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 by reproducing the zfs collector failure on FreeBSD stable/14 with the default node_exporter flags, then inspect the zfs collector's sysctl lookup. The issue mentions /usr/local/etc/rc.d/node_exporter only as a workaround; determine the intended handling for the missing sysctl and verify that the recurring collector error is resolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
observability, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.