-
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
Thread-level monitoring (similar to top -H) #5205
Comments
Would this be pulled into development anytime soon? |
I don't believe the library we are using, gopsutil, can get this information yet. Someone needs to investigate how this data can be acquired and propose a change to the gopsutil project, is this something you could do? |
I can do the investigation. But I am no expertise in Go :) |
It looks like the threads can be read in the same way to processes from |
At least on Linux, the thread info you are looking for is in The question I am struggling with is, how does one present the data? Are threads a property of the process? Or is it a separate accumulator metric? The change can be as easy as:
|
Feature Request
Telegraf procstat plugin helps to monitor various processes on the system, but does not take into account the multi-threaded processes (all running with the same main pid , but different thread ids)
In Linux, the "top -H" command gives a thread-level metric output.
Proposal:
Add a plugin or extension to procstat/processor plugin to enable thread-level monitoring
Current behavior:
Process-level aggregated output is displayed/stored
Desired behavior:
Thread-level output is desired
Use case: [Why is this important (helps with prioritizing requests)]
Many processes are multi-threaded and run on different cpus (or vcpus) , and the process output would be an aggregate of all .
The text was updated successfully, but these errors were encountered: