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: | |
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
[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.