Bug 534408 (RHQ-1207)

Summary: allow periodic reminders for recovery-based alerting
Product: [Other] RHQ Project Reporter: Joseph Marques <jmarques>
Component: AlertsAssignee: Charles Crouch <ccrouch>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: ccrouch, cwelton, hbrock, jshaughn
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: All   
URL: http://jira.rhq-project.org/browse/RHQ-1207
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-02 20:37:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 678340    

Description Joseph Marques 2008-12-03 16:50:00 UTC
I have two alert definitions:

to-be-recovered:= if { list of conditions }, disable until manually enabled by recovery alert or manually re-enabled
recovery alert:= if { other list of conditions }, re-enable <to-be-recovered>

when the to-be-recovered alert is triggered, it will send any notifications that are configured for it.  it might be useful to periodically push those notifications out again and again until the alert definition is recovered.  

we can extend recovery-based alert definition to have a new option:

re-notify every X units of Y time, until alert is recovered is re-enabled

then, when the to-be-recovered alert is triggered, we can create a periodic quartz job that will fire every X units of Y time.  when it fires, it will look up the current notification attached to the alert definition that created it, and re-notify those persons / devices.  when the recovery alert eventually triggers, it will unschedule this quartz job to stop the notifications.

Comment 1 Red Hat Bugzilla 2009-11-10 20:28:04 UTC
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1207