Bug 784687

Summary: Performance: Doc complex alert criteria
Product: [JBoss] JBoss Operations Network Reporter: Deon Ballard <dlackey>
Component: DocumentationAssignee: Deon Ballard <dlackey>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: JON 3.0.0CC: jkandasa
Target Milestone: ER01   
Target Release: JON 3.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-02 20:33:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Deon Ballard 2012-01-25 19:48:44 UTC 
Customers have set up alert defs with complex criteria, such as using metricX >= 5 AND metricX <= 10 to attempt to create a range. 

A variety of complex alert scenarios should be identified and documented up-front even if they do not work, just to establish known behavior.

See also:
https://engineering.redhat.com/trac/jon/ticket/10
Comment 1 Deon Ballard 2012-06-26 02:10:41 UTC 
Added an example on ranges here:
http://docs.redhat.com/docs/en-US/JBoss_Operations_Network/3.1/html/Admin_Setting_up_Monitoring_Alerts_and_Operations/alert-conditions.html#ex.alert-conditions

As these issues come up, I'll build out more examples.
Comment 2 Jeeva Kandasamy 2013-09-23 11:51:12 UTC 
Version: 3.2.0.ER1
Build Number: 54dd29c:464a643
GWT Version: 2.5.0
SmartGWT Version: 3.0

Doc link: https://access.redhat.com/site/documentation/en-US/JBoss_Operations_Network/3.1/html/Admin_Setting_up_Monitoring_Alerts_and_Operations/alert-conditions.html#ex.alert-conditions

Added alert definitions with complex criteria.