Bug 535340 (RHQ-2046)

Summary:	RFE: Allow an alert to trigger an operation n times and then give up
Product:	[Other] RHQ Project	Reporter:	Heiko W. Rupp <hrupp>
Component:	Operations, Alerts	Assignee:	Nobody <nobody>
Status:	NEW ---	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	jshaughn
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	All
URL:	http://jira.rhq-project.org/browse/RHQ-2046
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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