Bug 1036673 - Alert with avail_goes_not_up does not fire mutliple times when availability changes from DOWN to UNKNOWN
Summary: Alert with avail_goes_not_up does not fire mutliple times when availability c...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Monitoring - Alerts
Version: JON 3.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-02 13:13 UTC by Libor Zoubek
Modified: 2015-11-02 00:43 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-02 14:25:56 UTC
Type: Bug

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

Description Libor Zoubek 2013-12-02 13:13:10 UTC 
Description of problem:

This may be my wrong understanding of contition type AVAIL_GOES_NOT_UP. But I expect such alert to be fired anytime when availability of resource changes to state other than UP.


Version-Release number of selected component (if applicable):
JON 3.2.ER7

How reproducible: always


Steps to Reproduce:
1. have resource with availability UP
2. create alert definition for a resource with condition AVAIL_GOES_NOT_UP
3. set availability for resource as DOWN, wait 1 min
3. set availability for resource as UNKNOWN, wait 1 min

Actual results:

only 1 alert gets fired

Expected results:

2 alerts should be fired, because availability was changed twice to value other than UP
Comment 1 Libor Zoubek 2013-12-02 14:25:56 UTC 
works as expected. 

jshaughn> The resource will need to go back UP and then go DOWN again to generate a second alert
Note You need to log in before you can comment on or make changes to this bug.