prometheus / prometheus/node_exporter

Node exporter not picking up sensors output and hence sensors metrics are not exported

Open
#2,986 1 comment 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

We are running node_exporter in one of our linux machines and wanted to check the hwmon metrics. But, for some reason sensors data is not being exported.

The VM has a ASUS motherboard. Here is the output of dmidecode

Base Board Information
	Manufacturer: ASUSTeK COMPUTER INC.
	Product Name: PRIME X670-P WIFI
	Version: Rev 1.xx

Host operating system: output of uname -a

4.18.0-513.18.1.el8_9.x86_64 #1 SMP Thu Feb 1 03:51:05 EST 2024 x86_64 x86_64 x86_64 GNU/Linux

node_exporter version: output of node_exporter --version

node_exporter, version 1.3.1 (branch: tarball, revision: 4.el8)
build user:
build date: 20220128
go version: go1.16.12
platform: linux/amd64

node_exporter command line flags

node_exporter --web.listen-address=xx.xx.xx.xx:75622 --collector.textfile.directory=/var/lib/node_exporter/textfile_collector --collector.mountstats --collector.systemd --collector.hwmon

Are you running node_exporter in Docker?

No

What did you expect to see?

I expected to see the node_hwmon_fan_rpm and many other metrics but i don't actually see it.

Running sensors command directly on the VM does show me the FAN and temparature

sensors
enp8s0-pci-0800
Adapter: PCI adapter
PHY Temperature:  +51.0°C  
MAC Temperature:  +51.0°C  

nouveau-pci-0100
Adapter: PCI adapter
fan1:         993 RPM
temp1:        +30.0°C  (high = +95.0°C, hyst =  +3.0°C)
                       (crit = +105.0°C, hyst =  +5.0°C)
                       (emerg = +135.0°C, hyst =  +5.0°C)

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 report with the sensors command and node_exporter's --collector.hwmon entry point on the described Linux host. Compare the available sensor output with the exported metrics, including node_hwmon_fan_rpm; done means the relevant fan and temperature metrics are exposed or the unsupported sensor path is clearly identified.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.