Bug 535340 (RHQ-2046) - RFE: Allow an alert to trigger an operation n times and then give up
Summary: RFE: Allow an alert to trigger an operation n times and then give up
Keywords:
Status: NEW
Alias: RHQ-2046
Product: RHQ Project
Classification: Other
Component: Operations, Alerts
Version: unspecified
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL: http://jira.rhq-project.org/browse/RH...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-04-30 15:51 UTC by Heiko W. Rupp
Modified: 2023-01-20 05:19 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 534725 0 medium CLOSED how to handle known/to-be-expected outages? 2023-09-14 01:18:39 UTC

Description Heiko W. Rupp 2009-04-30 15:51:00 UTC
Suppose you have to restart a process due to some error condition as a reaction to a fired alert. 

Sometimes, the process does not come up again immediately (e.g. some needed network resource is not present). 

In this case we should allow to re-issue the operation n times with x seconds of pause in between.
If the process is still down after n iterations, RHQ should give up trying.

Actually, this behaviour is not Alert specific and should be available in plain operation scheduling as well.

Comment 1 John Mazzitelli 2009-05-14 17:17:18 UTC
so this would be an "operation retry" mechanism ?

Comment 2 Red Hat Bugzilla 2009-11-10 20:56:39 UTC
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2046


Comment 3 Heiko W. Rupp 2010-08-10 14:46:43 UTC
Actually that should go into a separate escalation framework and not into a single plugin, as retrying could be applicable for other alert senders too.

See also http://rhq-project.org/display/RHQ/Design+-+Alerts+future+enhancements


Note You need to log in before you can comment on or make changes to this bug.