You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Existing database queries use NOW() , UNIX_TIMESTAMP, etc. This makes it difficult to cater for different timezones. Case in point: the graphs can display UTC (or whatever timezone you choose), but the date picker on graph is always local time (for example).
My thoughts are that everything on the server should either be a unix timestamp (which are by nature timezone agnostic), or stored in the server timezone which is checked as part of the server validation. The translation needs to happen whenever a date is sent to or from a web page, converting to the user timezone when displayed, and converting to the server timezone when read from the browser.
Anything done on the CLI or server end (daily.php) will continue to use the server time, and all entries in the database should be stored in the server time.
So having said this, many of the files listed above should not be an issue. Is it possible to make a list within this ticket that we can tick off after checking each file?
The problem
Existing database queries use
NOW()
,UNIX_TIMESTAMP
, etc. This makes it difficult to cater for different timezones. Case in point: the graphs can display UTC (or whatever timezone you choose), but the date picker on graph is always local time (for example).Output of ./validate.php
What was the last working version of LibreNMS?
No response
Anything in the logs that might be useful for us?
The text was updated successfully, but these errors were encountered: