-
Notifications
You must be signed in to change notification settings - Fork 314
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle cpufreq files with <unknown> values. #304
Comments
Any progress on this issue ? |
I don't think so, feel free to submit a PR to fix this |
rexagod
added a commit
to rexagod/procfs
that referenced
this issue
Mar 19, 2024
Throw if file has non-numeric data, in addition to hinting the path that caused the error. Fixes: prometheus#304, prometheus/node_exporter#1710 Signed-off-by: Pranshu Srivastava <[email protected]>
rexagod
added a commit
to rexagod/procfs
that referenced
this issue
Mar 19, 2024
Throw if file has non-numeric data, in addition to hinting the path that caused the error. Fixes: prometheus#304, prometheus/node_exporter#1710 Signed-off-by: Pranshu Srivastava <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some systems produce
<unknown>
values for cpufreq files.See: prometheus/node_exporter#1710
The text was updated successfully, but these errors were encountered: