As I know time zone support in Zabbix 2.0/2.2 is somewhat "limited" I like to share my ideas.
Current state:
- zabbix utilizes UTC, that means all clock values in the DB are time zone adjustable
- time zone is set via a PHP variable and is valid per frontend
- some users suggest to have several frontends (virtual web servers, that is) with different set PHP values for time zone. That would lead to a bunch of distinct URLs, but is doable (e.g. /zabbix-CEST, /zabbix-GMT, /zabbix-PST and so on). For us this is no option.
Suggestion:
Zabbix devs would like to implements a time zone variable assignable to each individual host. If it is not set, simply use frontend's timezone variable (current behaviour).
- whenever an item belonging to this host is displayed/returned, a (defined) timezone variable is to be applied for TZ correction.
Any comments on that?
Thanks for your ideas!
Current state:
- zabbix utilizes UTC, that means all clock values in the DB are time zone adjustable
- time zone is set via a PHP variable and is valid per frontend
- some users suggest to have several frontends (virtual web servers, that is) with different set PHP values for time zone. That would lead to a bunch of distinct URLs, but is doable (e.g. /zabbix-CEST, /zabbix-GMT, /zabbix-PST and so on). For us this is no option.
Suggestion:
Zabbix devs would like to implements a time zone variable assignable to each individual host. If it is not set, simply use frontend's timezone variable (current behaviour).
- whenever an item belonging to this host is displayed/returned, a (defined) timezone variable is to be applied for TZ correction.
Any comments on that?
Thanks for your ideas!
Comment