-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
[0.10.3] current total CPU time is less than previous total CPU time #721
Comments
I don't think this is related to #720, but it might be. |
It comes from: cpu.go#L81-L84 Doesn't it recover after awhile? |
@david-AT That should happen only once, and then recover, can you give more details? |
@sparrc - What specific details would you like? I did just check the box again and the telegraf service has fallen over again:
|
Is your system operationally sound during this time otherwise? I'm curious why IOwait climbed in the middle of the night Would be helpful if you could run telegraf manually and get some debug output, like this:
|
closing for lack of info, please re-open if you can provide more details |
Debian 8. Brand new build.
CPU check was working fine. Then suddenly IOwait climbed rapidly in the middle of the night and the telegraf service stopped. (No error). Now on restart I have no CPU metrics. Here is an output:
And my config
The text was updated successfully, but these errors were encountered: