MySQL Bugs: #34240: Receive event alerts without acknowledging previous

Bug #34240	Receive event alerts without acknowledging previous
Submitted:	1 Feb 2008 19:20	Modified:	30 Apr 2010 11:02
Reporter:	Scott Noyes	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Advisors/Rules	Severity:	S4 (Feature request)
Version:	2.0.4.7141	OS:	Any
Assigned to:	MEM Service Manager Devs	CPU Architecture:	Any
Tags:	mem_auto_close

Description:
From support issue:

We want to watch for any changes to the database, including new tables, changed tables, etc. We get the warning, and it will not advise us of any changes after that until we have acknowledged. Once we have acknowledged it will continue to advise us of those changes from weeks back.

How to repeat:
Trigger multiple events of same type without acknowledging first one.

Suggested fix:
Change the monitor to just advise of changes after an acknowledgment and/or continue to advise even if acknowledgments have not been made.

Thank you for a reasonable feature request.

Raising Severety and Defect class because of following scenario (needs triage team to review it):

1. DBA receives email notification from MEM that sever is down
2. DBA resolves problem and server is up
3. DBA checks emails -> no notifications -> everything is OK
4. Server goes down again after one hour
5. DBA checks emails -> no notifications -> everything looks OK , but server is down

It is not obvious that after step 2) DBA *has* to go to dashboard and acknowledge notification to receive further *important* notifications.

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

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. The fix has been rectified through the implementation                                                                                      
        of the auto-close featurethat closes events once they have                                                                                         
        been cleared.