Bug #36606 Display Event Chain
Submitted: 9 May 2008 0:37
Reporter: Joshua Ganderson Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Enterprise Monitor: Server Severity:S4 (Feature request)
Version: OS:Any
Assigned to: Assigned Account CPU Architecture:Any

[9 May 2008 0:37] Joshua Ganderson
Description:
We currently have no way of knowing the state of an event over time (unless it's based on graphed values). This has been requested in the past (see bug 33826) and should not be difficult to add.

How to repeat:
Have an alarm go to warning, then to success, then to critical.

You have no insight into how this event behaved over time other than the last time it reached it's worst state and what it's currently at.

Suggested fix:
Add a tab to the event popup called "history" and display the state changes in a scrollable box. We may want to clip this if there are too many state changes for that event.

Also, the popup doesn't show the current state. It's trivial to add that in for completeness.

I'll likely need to work with Sloan or Oldag to get the history surfaced to the UI layer. On the other hand, I'm fairly sure we already store this info in an easily consumable format so it should not be difficult.