prometheus / prometheus/node_exporter
err="no CPU power status has been recorded" on M3
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 MacBook-Pro.local 23.1.0 Darwin Kernel Version 23.1.0: Mon Oct 9 21:32:11 PDT 2023; root:xnu-10002.41.9~7/RELEASE_ARM64_T6030 x86_64
node_exporter version: output of node_exporter --version
node_exporter, version 1.7.0 (branch: HEAD, revision: 7333465abf9efba81876303bb57e6fadb946041b)
build user: root@192f292aac5e
build date: 20231112-23:56:56
go version: go1.19.12
platform: darwin/amd64
tags: netgo osusergo static_build
node_exporter command line flags
What did you expect to see?
What did you see instead?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported node_exporter 1.7.0 behavior on the provided Darwin M3 environment and investigate the CPU power status entry point. The issue does not identify a file or test; done means CPU power status is recorded without the reported error on this platform.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, macos
- Domain
- observability, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100