-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Faulty values of system_p and user_p fields. #1610
Comments
Not sure if this will help, but could you try running topbeat with |
Thanks for response @ruflin :) But it brings no effects. Some records are ok, but most of them has wrong value - as before;/ |
Can you provide a gist with more output in it? Means multiple results for example for the cmdlin stress inside. A full debug log would be useful. |
@ruflin - I attache a file with redirected output of topbeats. I hope that You will have some ideas what can be root cause of such situation. |
For the first example you posted: Next example: This process is sleeping and it is not consuming any CPU time so all values are zero. The Attached file: There is a stress process with |
Hi All,
I've observed that topbeats get wrong values in my servers - especially fields system_p and user_p in cpu sections are wrong in my opionion. Despite of running "stress" process which generates enormous high cpu usage this statistics have zero-values. What can be a root cause of such situation? Below information about software/hardware and steps to reproduction. Thanks in advance for any hints.
Version: topbeat version 1.2.0 (amd64)
Operating System: Linux RedHat 2.6.32-573.18.1.el6.x86_64 #1 SMP Wed Jan 6 11:20:49 EST 2016 x86_64 x86_64 x86_64 GNU/Linux, 8-core machine.
Steps to Reproduce:
* type in CLI: stress -c 6 // predicted usage of cpu resources 75 %
* run topbeat as follows: topbeat -c topbeat.yml -e -d "*"
example output after above steps:
The text was updated successfully, but these errors were encountered: