Bug #23640 Problem resolution indication/notification
Submitted: 25 Oct 2006 17:43 Modified: 30 Apr 2010 11:05
Reporter: Sheeri Cabral (Candidate Quality Contributor) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor Severity:S4 (Feature request)
Version:mysqlnetwork-0.6.33, 2.0.5.7153 OS:Linux (Fedora Core 3 (i386))
Assigned to: Sloan Childers CPU Architecture:Any
Tags: qc

[25 Oct 2006 17:43] Sheeri Cabral
Description:
There's no indication when a problem has resolved.  In some cases, we'd want notification that the problem is no longer -- for instance, when the service is not reachable, replication not working.  Others, of course, we wouldn't.

For instance, I'd like the "server unreachable" issue to have an event when the server is reachable.  If there's a server outage I'd like to know how long that lasted.  I'd also like it to notify me (note that I'm not using Notifications yet, just going to the web interface, so I'm assuming that if an Event isn't thrown, a Notification won't be thrown either).

For some cases, I'd like to be able to automatically close an event if it's resolved.  Things like "server unreachable" and "excessive CPU usage" are useful to have in logs and see patterns, but I would want to configure a rule like "binary log not on" to just close itself when the binary log comes on again.

Flapping thresholds would be good too -- ie, automatically close the event the first and second times in 10 minutes it happens, but not any other times in the same 10 minute period.....

How to repeat:
Click on "Events" and you see events with a "close" tag, and the "close" button at the bottom.  There's no indication if a problem is still ongoing....
[26 Jul 2009 16:18] Valeriy Kravchuk
Thank you for the feature request.
[28 Apr 2010 14:42] Enterprise Tools JIRA Robot
Mark Leith writes: 
This has been resolved with the Auto-Close feature in 2.2.
[30 Apr 2010 11:05] MC Brown
A note has been added to the 2.2.0 changelog: 

        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.