Hi.
Monitoring hosts in a range of different Timezones brings to any Op team the usual 'what time has this happened anyways?' kind of problem.
Some Countries always have an UTC + 0 offset, others UTC + 9 offset, while others change twice per year (like our Server's location)
Would it be feasible to add some option on the Host Groups initial setup
to force its UTC offset as Country, City?
It could check some Olson timezone db library implementation like http://pytz.sourceforge.net/
The Monitoring | Latest data page could show the time in parenthesis or some other chosen tag so we would immediately know it doesn't share the Zabbix Server unixtime.
This would guarantee any historic and graph data correctness in an easy way for any Zabbix operator.
Monitoring hosts in a range of different Timezones brings to any Op team the usual 'what time has this happened anyways?' kind of problem.
Some Countries always have an UTC + 0 offset, others UTC + 9 offset, while others change twice per year (like our Server's location)
Would it be feasible to add some option on the Host Groups initial setup
to force its UTC offset as Country, City?
It could check some Olson timezone db library implementation like http://pytz.sourceforge.net/
The Monitoring | Latest data page could show the time in parenthesis or some other chosen tag so we would immediately know it doesn't share the Zabbix Server unixtime.
This would guarantee any historic and graph data correctness in an easy way for any Zabbix operator.