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
node_cpu_seconds_total reports incorrect cpu utilisation #581
Comments
Yes, I think you will need to upgrade your node_exporter version when it'll be released prometheus/procfs#438 [merged] This PR makes node_exporter to work correctly with offline-ed CPUs. I can confirm that the issue (most likely) connected with 4eed66b As a workaround you can turn on |
@vosdev if you'll try workaround, please report to us if it helps or not. |
I thought about that too. Thanks a lot for reporting this! I hope that folks from the Prometheus project will merge PR with fix soon.
Yep |
Aleksandr requested I create an issue on the LXD discuss (https://discuss.linuxcontainers.org/t/lxd-5-10-has-been-released/16143/9)
This morning my LXD snap updated from 5.9 to 5.10. Few minutes after the upgrade, my prometheus instance was firing my alert on all LXC instances, stating they are using 85-99% CPU:
100 - (avg by (instance) (irate(node_cpu_seconds_total{job="node-exporter",mode="idle"}[5m])) * 100) > 75
I have node_exporter running inside the LXC's, it is version 1.2.2.
My LXD snap is tracking latest/stable. This morning at 03:20 AM prometheus reported the high CPU usage on all my LXC instances. Their actual CPU usage is all below 5%.
The text was updated successfully, but these errors were encountered: