Bug 534398 (RHQ-1199)

Summary:	have CommandProcessor expose calltime metrics for each command type
Product:	[Other] RHQ Project	Reporter:	John Mazzitelli <mazz>
Component:	Communications Subsystem	Assignee:	John Mazzitelli <mazz>
Status:	CLOSED NEXTRELEASE	QA Contact:	Jeff Weiss <jweiss>
Severity:	medium	Docs Contact:
Priority:	low
Version:	unspecified	CC:	dajohnso
Target Milestone:	---	Keywords:	Improvement
Target Release:	---
Hardware:	All
OS:	All
URL:	http://jira.rhq-project.org/browse/RHQ-1199
Whiteboard:
Fixed In Version:	1.2	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description John Mazzitelli 2008-12-01 15:51:00 UTC

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).
Collect:

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

Comment 1 John Mazzitelli 2008-12-02 07:56:14 UTC

svn rev2159

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)

Comment 2 John Mazzitelli 2008-12-02 08:28:57 UTC

svn rev2160 fixes a bug in the 2159 checkin. therefore, 2160 goes hand in hand with 2159

Comment 3 Jeff Weiss 2009-02-09 17:01:35 UTC

The testing for rhq-1234 incorporates testing for this jira.  closing, rev2894

Comment 4 Red Hat Bugzilla 2009-11-10 20:27:54 UTC

This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1199
This bug relates to RHQ-1234