...
Users report problems relative to their timezone. Screenshots might be saved with timestamped filenames. "Things got really slow around 4pm" they'll say, and your job is to find what was happening on the server at 4pm.
I work on Linux, and my tooling hasn't evolved much since the 1970s. I don't know an easy way to convert log timestamps from UTC to something else, on the fly. If the log's timezone is that of the user, life is just easier.
| Note | ||
|---|---|---|
| ||
The lnav log file utility now reinterprets timestamps using the system timezone and |
The argument from Confluence developer laziness
...
To review, the timezone users see in Jira and Confluence comes from one of various levels:
| 1) User preference | Users can explicitly set their timezone in their profile:
| ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2) Default user preference | If your user preference isn't set, the default user preference will be in effect.
| ||||||||||||
3) Java user.timezone | The default user timezone preference inherits its value from the Java | ||||||||||||
| 4) OS timezone | Finally, Java sets its
|
So in Jira, everything is great. You can have atlassian-jira.log use a timezone that's good for debugging (UTC if that's your preference), while the default timezone used to render dates can be something appropriate for the majority of users.
...