Bug 582243

Summary:	RFE Add alert condition which compare one metric to another
Product:	[JBoss] JBoss Operations Network	Reporter:	dsteigne
Component:	Monitoring - Alerts	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED EOL	QA Contact:	Mike Foley <mfoley>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	JON 2.4.0, JON 2.4.2, JON 3.0.0, JON 2.4.1, JON 3.0.1, JON 3.1.0, JON 3.1.1	CC:	acavalca, bkramer, dmasirka, fbrychta, flo_bugzilla, genman, loleary, luc.douwen, myarboro, steven.post, tao, theute
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	JON 4.0.0
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-05 15:05:24 UTC	Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description dsteigne 2010-04-14 13:27:49 UTC

When I configure an alert's template on Datasource resource, it seems to be inpossible to fire the alert when active connections represents 50% of the max-pool-size. I've tried to do it with "active Connections > 50.0% of Max Value" but Max Value, here, is not the max-pool-size.
The only solution I see for the moment is to make an alert on absolute value but, as the value max-pool-size is not the same on every datasource, it could be a heavy work to configure this alert on each datasource manually (and we loose the great advantage of templates to have automatic alerting for coming new datasource)

Comment 1 Lukas Krejci 2011-01-20 20:50:37 UTC

This is going to be hard(ish).

AFAIK, the alert subsystem condition cache assumes that a value to compare a metric with is stored in the condition itself.

What is required here is that both values to be compared come from the measurement report. Today the conditions are checked in a very "simple" manner by merely iterating over a set of measurements and checking conditions for each by comparing the measured value with the value stored in the condition. 

We'd need a new type of alert condition that would not hold a value but would provide a matches() method that would take in two values. We'd also need a lookup mechanism to obtain the two values to match. The trouble is that there is no guarantee that the two values that should participate in the condition are going to be in the set of the processed measurements (the agent plugins are free to not provide a metric value when asked for it). Therefore we'd need another DB/cache lookup of the value before we could pass it to the condition "processor". 

Note that because of the nature of the measurement collection there would be no difference between comparing values coming from the same resource and values from different resources.

Comment 2 Larry O'Leary 2011-11-21 15:40:24 UTC

Please note that this RFE is for all metrics and the datasource metric provided in the description is only an example.

Comment 3 Charles Crouch 2011-12-20 20:50:28 UTC

worked with lukas directly

Comment 5 Larry O'Leary 2013-06-03 18:58:52 UTC

Moving to JBoss ON BZ as this is from downstream.

Comment 6 Thomas Heute 2013-07-26 13:28:25 UTC

Larry, I think we agreed to deferred that one ?

Comment 7 Larry O'Leary 2013-07-26 15:40:10 UTC

From PRODMGT-31 this was accepted and would be considered as part of the 4.0 payload.

Comment 10 Filip Brychta 2019-08-05 15:05:24 UTC

JBoss ON is coming to the end of its product life cycle. For more information regarding this transition, see https://access.redhat.com/articles/3827121.
This bug report/request is being closed. If you feel this issue should not be closed or requires further review, please create a new bug report against the latest supported JBoss ON 3.3 version.