prometheus / prometheus/node_exporter

Darwin M1 temperature reading via SMC

Open
#2,639 4 comments 4 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

Darwin de-unit-1032.mu4 22.3.0 Darwin Kernel Version 22.3.0: Mon Jan 30 20:39:35 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T8103 arm64

node_exporter version: output of node_exporter --version
node_exporter, version 1.3.1 (branch: HEAD, revision: a2321e7b940ddcff26873612bccdf7cd4c42b6b6)
  build user:       root@e7da778d77e0
  build date:       20211205-11:13:28
  go version:       go1.17.3
  platform:         darwin/arm64
Are you running node_exporter in Docker?

no

What did you expect to see?

This is a feature request to support reading temperature/fans metrics from Apple SMC. This is currently seems to be a universal solution for both Intel and Apple Silicon hardware.
Example of working go code could be seen in: https://github.com/dkorunic/iSMC
I believe this support would be highly appreciated by all of the mac farm build agents owners.

What did you see instead?

No any temperature reading from node_exporter on darwin.

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 reviewing node_exporter’s existing Darwin collectors and the working Go example in dkorunic/iSMC, using the reported Darwin arm64 environment as the target. Determine how temperature and fan metrics should be exposed for Apple SMC on Intel and Apple Silicon, then validate that node_exporter reports those metrics on Darwin.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.