Red Hat Bugzilla – Bug 534398
have CommandProcessor expose calltime metrics for each command type
Last modified: 2014-11-09 17:48:08 EST
Currently, CommandProcessor collects average execution time metrics for successfully executed commands. But on a stable system, the value is usually "0" or close to it because the majority of its messages are pings and are very fast.
It would be nice to have it collect metrics on a per command type (and for remote pojos, collect down to the method being invoked).
command type|sub command type|max time|min time|average time
Have aggregated RemotePojo invocations but the sub command type would be the class.method name
we now have calltime metrics being collected for each individual command type/remote pojo. for use with rhq-plugin (see https://jira.jboss.org/jira/browse/JOPR-30)
svn rev2160 fixes a bug in the 2159 checkin. therefore, 2160 goes hand in hand with 2159
The testing for rhq-1234 incorporates testing for this jira. closing, rev2894
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1199
This bug relates to RHQ-1234