Bug 746337 - need metric baseline range conditions
need metric baseline range conditions
Status: NEW
Product: RHQ Project
Classification: Other
Component: Core Server (Show other bugs)
unspecified
Unspecified Unspecified
medium Severity high (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-10-14 16:08 EDT by John Mazzitelli
Modified: 2011-10-19 10:58 EDT (History)
2 users (show)

See Also:
Fixed In Version:
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: ---


Attachments (Terms of Use)

  None (edit)
Description John Mazzitelli 2011-10-14 16:08:23 EDT
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.