prometheus / prometheus/procfs
Handle cpufreq files with <unknown> values.
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 883
- Forks
- 388
- Avg merge
- 13h 28m
- Merged PRs (30d)
- 3
Description
Some systems produce <unknown> values for cpufreq files.
See: https://github.com/prometheus/node_exporter/issues/1710
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 reviewing the linked prometheus/node_exporter issue 1710 and locating the cpufreq file parsing entry point in this procfs repository. Determine how values should be handled, then verify that cpufreq data is processed without failure for those inputs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100