MySQL Bugs: #32615: wrong information due to different timezones between agents and server

Bug #32615	wrong information due to different timezones between agents and server
Submitted:	22 Nov 2007 10:55	Modified:	12 Jun 2009 12:54
Reporter:	Ted Wennmark	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor	Severity:	S3 (Non-critical)
Version:	1.2.0.7897	OS:	Linux (RHES5)
Assigned to:	Mark Matthews	CPU Architecture:	Any

Description:
I have set up MySQL Network Monitor and have som problem.

Setup:
4 machines running mysql and agents (all machine have diffrent timezone)
1 machine running the "monitor server"

When looking att the GUI there are loots of things not looking so good, can I tell the server that my agents are running in a different timezone from the server so that for example the Meta information does not say that it was 5 hour since last mysql contact, the same problem with agent contact but there is a green light so it seems to work for that.

It is hard looking at graphs if you can't tell the server what timesone the agent is running in.

This also impact the replication, seconds behind master does not work when the agents are in different timezones.

How to repeat:
Install MySQL Network and Monitor and run agents in different timezones.

The agents and the server all report times in UTC, so I'm not quite sure what the issue is here. Maybe a UI bug, since that's where the transform to an actual timezone happens?

The issue is that the GUI for the Enterprice monitor which is MySQL:s product does not handle timezones correctly if you set it up as described.

We won't be fixing this in the 1.x branch.  

Many UI related timezone issues have been fixed.  I suggest trying to do some timezone testing for 2.1 and if we can't reproduce let's close this one out.

I've tested the current 2.x with different time zones for multiple agents and also each a different TZ for both the systems where the MEM server is running and the other system where the browser with the dashboard was located. I could not see any problems, even when changing the TZ on an agent's system forward and backward. Changing the TZ for the user in the dashboard changed the shown times as expected. From this I close this problem.

Please feel free to re-open this bug if you see problems like you had seen in the past also with the current 2.x version. If this is the case we kindly ask to receive a detailed problem description / steps how you had setup your system, so that we are able to reproduce the problem in our test lab.