-
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
Support metrics for offline CPUs #84
Comments
As I wrote in #873, an option/fix would be iterating over the
|
Thanks for the information @mjtrangoni. I took the liberty to rename the issue a bit. There is no support for offline CPUs availble in this procfs library at the moment. Furthermore, the node_exporter doesn't currently use this procfs library for CPU metrics, but this is something we should change. Your |
Thanks for the clarification @mjtrangoni, my bad, I had missed that the node_exporter uses procfs by now. In either case, I don't think that the procfs library does anything wrong here, it's meant to be a library to access procfs information from go. It would be the node_exporter's responsibility to combine the information from |
What I think is wrong or not 100% right is that, in my case, all intermediate metrics of offline CPUs are initialized to 0, while the ones from cpu154 onwards are not. I have to double-check that! |
You're right, we're currently exposing an array with zero value |
Hi @rtreffer @SuperQ ,
This issue is related to #873.
When parsing the
/proc/stat
file, I am missing the latest offline CPUs bunch of metrics (from cpu154 to cpu159). As @brian-brazil said, the CPU metrics should always be there.See:
Summarizing, every CPU metrics of an offline CPU until cpu151 are zero, while the last bunch cpu{154..159} are missing completely .
The text was updated successfully, but these errors were encountered: