Bug 784687 - Performance: Doc complex alert criteria
Summary: Performance: Doc complex alert criteria
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Documentation
Version: JON 3.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER01
: JON 3.2.0
Assignee: Deon Ballard
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-25 19:48 UTC by Deon Ballard
Modified: 2014-01-02 20:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-02 20:33:48 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.