Bug #26553 Events that escalate in Severity are not sent as email notifications
Submitted: 22 Feb 2007 4:00 Modified: 3 May 2007 22:02
Reporter: Bill Weber Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Server Severity:S3 (Non-critical)
Version:1.1.0.4810 OS:Any
Assigned to: Darren Oldag CPU Architecture:Any
Tags: mer 111

[22 Feb 2007 4:00] Bill Weber
Description:
If an Event has escalated in Severity (ie from Warning to Critical), another email with the more severe alert is not sent.

How to repeat:
- set max_connections for monitored server to 20 and restart server
- setup Dashboard to send email notifications
- schedule Heat Chart - Connection Usage Excessive rule
- increase connections to 18 to generate a Warning Event for Heat Chart - Connection Usage Excessive and also send an email with the Warning
- increase connections to 20 to generate a Critical Event for Heat Chart - Connection Usage Excessive and notice that no email is sent with Critical
[2 Mar 2007 20:06] Sloan Childers
This is a *must* fix for 1.1.1
[22 Apr 2007 0:45] Darren Oldag
code is fixed in trunk.  patch submitted for review for inclusion into merlin 1.1.1 release.
[27 Apr 2007 21:13] Darren Oldag
patch committed to 1.1.1 branch.
[3 May 2007 21:26] Andrew Cwik
fixed in build 1.1.1.5336.
[3 May 2007 22:02] Peter Lavin
Added to the changelog.