Opened 3 years ago
Last modified 3 years ago
#817 assigned defect
CurrentThreadCpuTime graph of JMX plugin doesn't show a well-defined value
| Reported by: | jsa | Owned by: | knan |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | plugins | Version: | 1.4.2 |
| Severity: | normal | Keywords: | |
| Cc: |
Description
The CurrentThreadCpuTime? graph of the JMX plugin shows a ill-defined value at best and can be considered useless.
Since the value is aquired via a remote JMX connection, the thread that is actually checked is undefined and most likely to be some JMX service thread.
Therefore the value retrieved by this plugin is pretty much random and can only serve as a very low lower barrier of the CPU time used by the JVM.
A more useful plugin would measure the CPU time of a thread (or even multiple threads) defined by some regex matching on the threads names.
Change History (3)
comment:1 Changed 3 years ago by janl
- Milestone Munin 1.5 deleted
- Owner changed from nobody to knan
comment:2 Changed 3 years ago by knan
- Status changed from new to assigned
comment:3 Changed 3 years ago by jsa
I can see myself helping with the JMX plugins a bit, since I use them at work and may find some time here.
I don't need this specific feature, so it's rather far down on my list.

CurrentThread?* being useless may be true. And your proposed new plugin sounds like useful functionality, yes. Are you volunteering? We could use the help :)
http://nadeausoftware.com/articles/2008/04/java_tip_how_list_and_find_threads_and_thread_groups
... may be a good start.