Bug #27132 "Slave Has Been Stopped" should automatically close when recovery is detected

• Submitted: 14 Mar 2007 13:22
• Modified: 30 Apr 2010 11:40
• Reporter: Johan Idrén
• Status: Closed
• Category: MySQL Enterprise Monitor: Advisors/Rules
• Severity: S4 (Feature request)
• Version: 1.1.0
• OS: Any
• Assigned to: Sloan Childers
• CPU Architecture: Any

[14 Mar 2007 13:22] Johan Idrén

Description:
When a rule, for example "Slave Has Been Stopped", you need to manually close the incident even if the server recovers.

How to repeat:
Monitor a server with replication slave, stop slave, wait for Dashboard to trigger an alert, start slave again.

Status of monitored test will not recover, even though event is no longer critical.

Suggested fix:
Alerts that can recover, for example "Slave Has Been Stopped", should do so. Maybe going into a special status for "was critical, please review". Or just being reverted back to warning

This behaviour would make it much easier to locate critical issues that are critical when viewing the dashboard, not things that were critical 15 minutes ago, potentially saving time when doing emergency fault finding.

[28 Apr 2010 14:41] Enterprise Tools JIRA Robot

Mark Leith writes: 
This has been resolved with the Auto-Close feature in 2.2.

[30 Apr 2010 11:40] MC Brown

When events have been raised by &merlin;, new events of the same                                                                                   
        type would not be notified until the original event had been                                                                                       
        acknowledged. This could lead to critical events being missed.                                                                                     
        In addition, when viewing existing events that have been                                                                                           
        triggered, it is impossible to know if the notified event is                                                                                       
        still causing a problem.                                                                                                                           
                                                                                                                                            
        The fix has been rectified through the implementation of the                                                                                       
        auto-close feature on events. With this feature enabled, events                                                                                    
        will automatically be closed once the event is not longer                                                                                          
        identified as causing a problem.