The default time zone we use to translate timestamps into readable formats and also for filtering is the time zone of your browser setting.
Because machines can be located in different time zones we save all timestamps as Unix timestamps, so there can be no mix-ups. But if you are looking at a machine which is not in your time zone and you filter for the data of a specific day, you might not want to filter for "your day" but for the "day" of the machine. To do so you can enable the time zone setting on your dashboard and select the time zone of the machine.
...
The names used for the time zones originate from the tz-database. If you select a time zone not only the display of timestamps will be affected but also the range of some filter (e.g. today, this week, last month, etc.) and the grouping of timestamps.
Note that if "None" is selected as a time zone, then the time zone of the browser settings is used. Just as for filters you can define a default time zone for each section by selecting a time zone in the settings.
| Note |
|---|
Note that these timezone settings are applied to datasets directly used in widgets but also to datasets used in scripts. So be careful with date-time conversions in scripts that require time zone settings. So for example, if you are changing the time zones applied to the datasets, but you are using a hard-coded timezone in your script the result might be not as expected. |