History | Log In     View a printable version of the current page.  
HQ 4.0 EE Release is Now Available | HQ 3.2.5-EE Maintenance Release is Now Available
Issue Details (XML | Word | Printable)

Key: HHQ-1641
Type: New Feature New Feature
Status: Closed Closed
Resolution: Fixed
Priority: Critical Critical
Assignee: Charles Lee
Reporter: John Sachs
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Hyperic HQ

Allow admins to configure looping escalations

Created: 14/Feb/08 08:07 AM   Updated: 07/Jul/08 10:03 AM
Component/s: None
Affects Version/s: 3.2.0
Fix Version/s: 4.0.0, 3.2.4

Verify By: Nipuna Bhayani
Last comment: 19 weeks, 4 days ago
Resolution Date: 30/May/08 07:53 PM


 Description  « Hide
In the case where the end of an escalation scheme is reached and the alert condition still exists, HQ currently fires a new alert and essentially starts the escalation over. This has a negative side effect of cluttering the alert center with several unfixed alerts for the same "event".

Admins should have the option of either configuring the escalation scheme to loop or to add a step in the scheme which causes it to loop. This would have the same effect notification-wise as the current alert implementation, but would not cause HQ to fire a new alert. This would make it much easier for admins to review their alert history and current alerts in the alert center.

We may want to review this for possible change to the default alert behavior in HQ.

 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Ryan Morgan - 14/Feb/08 02:39 PM
Assign to Chip for product backlog.

Ryan Morgan - 21/Feb/08 09:44 AM
Unset fix version. This is in the product backlog.

Charles Lee - 30/May/08 07:53 PM
Added option to repeat escalation actions if alert remains unfixed.

Nipuna Bhayani - 07/Jul/08 10:03 AM
Looping Escalation functionality is available in 3.2.4 release