Bug 771762

Summary:	Improvements Needed to Increase Usefulness/Useability of Custom RHQ Plugins
Product:	[Other] RHQ Project	Reporter:	Ted Jones <tejones>
Component:	Plugins	Assignee:	Nobody <nobody>
Status:	NEW ---	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.3	CC:	hrupp, tcunning
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
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:
Bug Depends On:	536280, 578972, 796480
Bug Blocks:

Description Ted Jones 2012-01-04 21:31:45 UTC

Description of problem: There are several issues that need to be addressed to make custom plugins more useful. This is the top level BZ to track issues identifying required functionality and other improvements. 


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 tcunning 2012-01-05 21:11:39 UTC

I added https://bugzilla.redhat.com/show_bug.cgi?id=536280 as a proxy for the improvements described here : 

http://www.rhq-project.org/display/RHQ/Design-Dynamic+Metadata

Dynamic metrics would make it possible to do BAM-style tracking in RHQ.

Comment 2 Edson Tirelli 2012-01-05 21:46:52 UTC

In addition to dynamic metrics previously mentioned, specially for JMX-based use cases, RHQ should be able to monitor short-lived resources. 

For instance, in Drools/Hibernate/etc, where you have sessions being created and disposed all the time, the typical interval based (24hs default) discovery cycle is not enough. 

My suggestion would be the ability to define bean name patterns, and discover any beans matching those name patterns every time metrics are collected. This will allow RHQ to aggregate metrics from multiple short-lived resources (like Drools sessions) into their views and graphs.