Bug 1028473

Summary: Availability duration alerts ignore availability changes during the specified interval
Product: [Other] RHQ Project Reporter: Jay Shaughnessy <jshaughn>
Component: AlertsAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Jay Shaughnessy <jshaughn>
Severity: high Docs Contact:
Priority: high    
Version: 4.9CC: hrupp
Target Milestone: GA   
Target Release: RHQ 4.10   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1028526 (view as bug list) Environment:
Last Closed: 2014-04-23 12:31:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1028526    

Description Jay Shaughnessy 2013-11-08 14:25:22 UTC 
Availability duration alerts ignore availability changes during the specified interval.

This was actually part of the original design but has turned out to be a liability.  As an example, consider a "Stays Down for 10 Minutes" avail duration condition.

When a 'Goes Down' avail change is detected for resource X it starts the 10 minute interval.  When the 10 minute interval completes, if the the current availability for X is 'Down' then the condition is satisfied (and typically an alert is fired, as these are usually single-condition alert definitions).

But what if during that 10 minutes X actually came up and then went down again?  In this case the alert would have fired but it really should not have.  It did not *stay down* for 10 minutes.  In fact, the second time it went down another 10 minute interval will have started.

The expectation is that the "stays down" or "stays not up" semantic is strictly followed.
Comment 1 Jay Shaughnessy 2013-11-08 15:58:32 UTC 
master commit d5825367a91de8b8adc4491dae354aeb10802ae4
Author: Jay Shaughnessy <jshaughn>
Date:   Fri Nov 8 10:42:16 2013 -0500

Fixed such that avail duration conditions will not be satisfied unless the
avail stays constant throughout the specified time interval.

Also: Fix a jdoc mistake around param units in AvailabilityCriteria
Comment 2 Heiko W. Rupp 2014-04-23 12:31:45 UTC 
Bulk closing of 4.10 issues.

If an issue is not solved for you, please open a new BZ (or clone the existing one) with a version designator of 4.10.