Bug #32016 Events list doesn't take into account DST when sorting events by time
Submitted: 1 Nov 2007 0:48 Modified: 14 Oct 2008 17:00
Reporter: Bill Weber Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Web Severity:S3 (Non-critical)
Version:1.2.0.7879 OS:Any
Assigned to: Mark Matthews CPU Architecture:Any

[1 Nov 2007 0:48] Bill Weber
Description:
The Events list does not take into account Daylight Time vs Standard Time when list ing events that happened during both 1:00am-1:59am times. So an event which occurred at 1:10am Standard Time will be listed before an event that occurred 50 minutes before it at 1:20am Daylight Time.

How to repeat:
- set clock to an hour before Standard Time begins (e.g. Nov 4th 1:00AM)
- start dashboard
- cause an event (EventA) to fire at 1:20AM Daylight Time
- wait 50 mins until 1:10AM Standard Time (or manually set system clock)
- cause another event (EventB) to fire at 1:10AM Standard Time
| notice EventB is listed before EventA
[13 Mar 2008 22:56] Joshua Ganderson
According to Oldag, the event dates are now stored at bigint ms and DST should no longer be an issue.
[13 Aug 2008 0:47] Bill Weber
fixed in pre-release 2.0 build 2.0.0.7023
[14 Oct 2008 17:00] Tony Bedford
An entry was added to the 2.0 changelog:

The Events list did not take into account Daylight Time and Standard Time when listing events that happened during 1:00am-1:59am. An event that occurred at 1:10am Standard Time was listed before an event that occurred 50 minutes before it at 1:20am Daylight Time.