Bug #26349 Event details show inaccurate Notification information
Submitted: 13 Feb 2007 23:50 Modified: 22 Jul 2008 11:15
Reporter: Kolbe Kegel Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Server Severity:S3 (Non-critical)
Version:1.0, 2.0 OS:Linux (Linux)
Assigned to: Darren Oldag CPU Architecture:Any

[13 Feb 2007 23:50] Kolbe Kegel 
Description:
When viewing the Results of an Event in the Events tab of the Dashboard, the Notifications section does not reflect the Notifications settings at the time the Event was triggered, but rather the Notifications settings at the time the Event Results are viewed.

How to repeat:
1. Set up an Advisor with no Notification settings
2. Cause the above mentioned Advisor to trigger an Event
3. View the Results tab for the above mentioned Event by clicking on the relevant Rule name in the Events tab
4. Note the contents of the Notifications field
5. Modify the Advisor created in step #1 to include some Notification Group
6. Repeat steps 2-4 and compare results of step #4

In the first case, the Notifications section will say "No notifications set". In the second case, the Notifications section will reflect the newly configured Notification settings even though the event was triggered long ago.

Suggested fix:
The Event Results in the Events tab should show accurate *historical* information that can be used to determine whether a particular Event caused any email Notifications to be sent.

This would require such historical information to be stored somewhere, of course. That would have other positive side effects as well.
[2 Mar 2007 20:06] Sloan Childers 
This is a *must* fix for 1.1.1
[2 May 2008 5:25] Gary Whizin 
Re-opening to force bug triage :)
[28 May 2008 16:39] Darren Oldag 
fixed in 2.0.  will likely not fix for 1.x.
[3 Jun 2008 0:29] Bill Weber 
verified fixed in 2.0.0.6047
[22 Jul 2008 11:15] Tony Bedford 
An entry was added to the 2.0 changelog:

When viewing the Results of an Event in the Events tab of the Dashboard, the Notifications section did not reflect the Notifications settings at the time the Event was triggered, but rather the Notifications settings at the time the Event Results were viewed.