Bug 746337 - need metric baseline range conditions
Summary: need metric baseline range conditions
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Core Server
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-14 20:08 UTC by John Mazzitelli
Modified: 2022-03-31 04:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 735262 0 high CLOSED alert def with multiple conditions using the same metric fires alerts at wrong times 2021-02-22 00:41:40 UTC

Internal Links: 735262

Description John Mazzitelli 2011-10-14 20:08:23 UTC
bug #735262 showed that the condition processing of metric values need to not assume multiple AND conditions on the same metric can product the desired effect.

That bug was fixed with the new range condition. For example, rather than creating an alert definition with two conditions with the AND conjunction (aka "ALL):

if metric A > 50
AND
if metric A < 100

instead you can now have one condition with a range:

if 50 < metric A < 100

However, this new range condition only supports absolute metric values.

This issue asks that we add another new type of alert condition to support metric BASELINE ranges. Specifically, we want to go from this:

if metric A max baseline value > 10%
AND
if metric A max baseline value < 30%

we want a new baseline range condition that allows for a single condition that says:

if 10% < metric A max baseline value < 30%

This is to address the same issue that bug #735262 reported.


Note You need to log in before you can comment on or make changes to this bug.