Bug #46143 Thresholds have random ordering in email alerts

• Submitted: 13 Jul 2009 9:24
• Modified: 22 Jul 2009 10:10
• Reporter: Mark Leith
• Status: Closed
• Category: MySQL Enterprise Monitor: Server
• Severity: S3 (Non-critical)
• Version: 2.1.0.1074
• OS: Any
• Assigned to: Eric Herman
• CPU Architecture: Any

[13 Jul 2009 9:24] Mark Leith

Description:
The threshold information in email alerts lists the thresholds in a random order, some samples:

Thresholds 
Warning : 1024 
Info : 512 
Critical : 10240 

Thresholds 
Info : 70 
Critical : 5 
Warning : 40

Thresholds 
Critical : 75 
Warning : 85 
Info : 95 

How to repeat:
o Enable email alerts to an email address
o Enable all rules, the above three are from the following, respectively:

Slave Execution Position Too Far Behind Read Position 
CPU Usage Excessive
Key Buffer Size May Not Be Optimal For Key Cache

o Make the rules fire
o Check the email alerts for the threshold listings

Suggested fix:
Order in terms of severity:

Info
Warning
Critical

[14 Jul 2009 13:14] Enterprise Tools JIRA Robot

Eric Herman writes: 
alarm emails will now show thresholds sorted in the same order as RuleEvaluator uses (which is "worst first" by severity)

[15 Jul 2009 19:35] Enterprise Tools JIRA Robot

Keith Russell writes: 
Patch installed in versions => 2.1.0.1077.

[15 Jul 2009 20:34] Enterprise Tools JIRA Robot

Marcos Palacios writes: 
Verified fixed in build 2.1.0.1077.

[22 Jul 2009 10:10] Tony Bedford

An entry was added to the 2.1.0 changelog:

The threshold information in email alerts listed the thresholds in a seemingly random order, for example:

Thresholds 
Warning : 1024 
Info : 512 
Critical : 10240 

Thresholds 
Info : 70 
Critical : 5 
Warning : 40

Thresholds 
Critical : 75 
Warning : 85 
Info : 95