prometheus / prometheus/node_exporter

FreeBSD rc.d system collector missing

Open
#2,219 3 comments 1 reaction 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

step01 ~ » uname -a
FreeBSD step01.infra.isi.ca 12.2-RELEASE-p7 FreeBSD 12.2-RELEASE-p7 GENERIC amd64

node_exporter version: output of node_exporter --version

step01 ~ » node_exporter --version node_exporter, version 1.2.2 (branch: release-1.2, revision: 0) build user: root build date: go version: go1.17 platform: freebsd/amd64

node_exporter command line flags

step01 ~ » cat /etc/rc.conf | grep node
node_exporter_enable="YES"
node_exporter_args="--no-collector.zfs"

Are you running node_exporter in Docker?

No

What did you do that produced an error?

No error.

What did you expect to see?

It would be nice to have a collector for FreeBSD rc.d sytem so we can monitor services directly with node_exporter.

What did you see instead?

N/A

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

The issue names no files, tests, or entry points. Start by reviewing node_exporter's existing collector structure and FreeBSD rc.d service interface; clarify which service states and metrics are required, then add coverage and verify the collector reports them.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.