[ZBXNEXT-333] Timezone setting for users Created: 2010 Apr 27  Updated: 2021 Sep 30  Resolved: 2021 Sep 30

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: New Feature Request Priority: Major
Reporter: Cal Sawyer Assignee: Unassigned
Resolution: Fixed Votes: 36
Labels: timezone
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates ZBXNEXT-250 Need to have possibility to define ti... Closed
is duplicated by ZBXNEXT-1144 Time zone for users in different time... Closed

 Description   

It would good to be able to establish a timezone for hosts that could be used as an (optional?) offset in Graphs (and other places?) so that data is shown correlated with the location/time of the hosts, not the local TZ.



 Comments   
Comment by David M. Zendzian [ 2011 Sep 13 ]

I would propose that instead of a timezone setting for a host having it for the user account and keep all hosts in GMT that way each zabbix user would view events in the time that's relevant to them.

Comment by saif [ 2013 Feb 11 ]

Please implement User account wise timezone setting so that users can see monitoring data on their own timezone, this is very basic requirement for web application and most of the web app having this, so please work on it and make zabbix better...

Thanks

Comment by Clark Ritchie [ 2013 Aug 29 ]

I agree, this is an essential feature. We are using 2.0.8 and it seems there is still no facility to do this on a per-user basis.

Comment by Marc [ 2013 Aug 29 ]

I think considering local (Web browser) timezone is a nice feature.
If implemented it should be able to:

  • pre-define it globally (including option to ask on first logon)
  • configure it in user profile (including option to use 'Accept-Language' header)
Comment by Andris Bjornson [ 2013 Aug 30 ]

+1 for this feature. We monitor hosts in many timezones on the same Zabbix server and have to communicate with providers in each when there are issues. It would be ideal to be able to share graphs relevant to each provider with times in their own timezone.

Comment by saif [ 2013 Aug 30 ]

+1, This is really important and very basic feature should be available on zabbix.
Thanks

Comment by Dmitry [ 2013 Sep 13 ]

+1, it is strange that so few people vote here.

Comment by Fabian van der Hoeven [ 2014 May 07 ]

+1, would be very usefull! Global economy and stuff...

Comment by Marian Rychtecky [ 2014 Jul 01 ]

+1, I would like to ask you implement this feature, this is very important for me. Thanks!

Comment by richlv [ 2014 Jul 01 ]

please see https://www.zabbix.org/wiki/Docs/bug_reporting_guidelines#Reporting_an_issue and note that "me too" comments only clutter issues and waste developer time

Comment by richlv [ 2016 Mar 08 ]

ZBXNEXT-250 asks for per-user timezone

Comment by richlv [ 2016 Mar 08 ]

per-host timezone setting could have some confusing/unclear/risky aspects. for example, what about maintenance ?

Comment by Javier Spagnoletti [ 2016 Apr 15 ]

Alexei Vladishev, this feature at least should be considered in order to provide different time zones between the frontend app and the API. Do you have any ETA or roadmap for this ticket?

Regards.

Comment by richlv [ 2016 Apr 15 ]

phansys, you are probably interested in ZBXNEXT-250 - and the user reference you have in there does not seem to have worked

Comment by Javier Spagnoletti [ 2016 Apr 15 ]

richlv, that's not my use case. Indeed, I'm fine if I can configure only 2 TZs: one for the frontend web application and other for the API. I'm pretty sure that having one TZ for frontend user will be better in order to allow globally distributed teams to get accurate dates; but applications cosuming APIs are responsible in the majority of situations to handle these TZs according its own needs.

Comment by richlv [ 2016 Sep 23 ]

timezone-related issues :

Comment by Alexei Vladishev [ 2021 Sep 30 ]

Support of per-user timezones has been implemented under ZBXNEXT-250 in Zabbix 5.2.

Generated at Fri Apr 19 03:14:38 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.