| Bug #39504 | Alerts sent from MEM uses GMT timezone, not user/server timezone | ||
|---|---|---|---|
| Submitted: | 17 Sep 2008 21:12 | Modified: | 22 May 2009 13:53 | 
| Reporter: | Alexander Rubin | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Enterprise Monitor: Configuration | Severity: | S4 (Feature request) | 
| Version: | OS: | Any | |
| Assigned to: | Sloan Childers | CPU Architecture: | Any | 
| Tags: | mem, timezone | ||
   [17 Sep 2008 21:12]
   Alexander Rubin        
  
 
   [8 May 2009 23:24]
   Sloan Childers        
  Added support to 1.3 and 2.x branches to show the GMT and MEM server local times in alerts.
   [11 May 2009 15:32]
   Marcos Palacios        
  Tested with build 2.0.5.7153. Found out that the fix was checked into the 2.1 release ("not in the maintenance release").
Testing in 2.1 now...
 
   [11 May 2009 16:07]
   Marcos Palacios        
  Verified fixed in service manager build 2.1.0.1036.
   [22 May 2009 13:53]
   Tony Bedford        
  An entry was added to the 2.1.0 changelog: Alerts sent from MySQL Enterprise Monitor used the GMT timezone, for example: Time: 2008-09-17 19:41:08 GMT That was not convenient for users, as their timezones may not have been GMT.
