Change date formats in logging to use RFC3339#434
Change date formats in logging to use RFC3339#434dBotLFG wants to merge 2 commits intoaws:mainlinefrom
Conversation
|
Hi @dBotLFG, what the reason to do this? Is it not enough to set the system time to UTC? |
|
If the system time is set to local, the logs will use local time, but the timestamp will not reflect that it is local time (no offset indicator). By using a UTC timestamp by default, there will be no ambiguity in the time of the logged event. At a minimum, there should be a timezone offset used by default. As the code currently stands, it would be very difficult to correlate events between instances located in different regions with different timezones. Thank you for your consideration. |
In a default configuration, I always expect this. Each system component is logging in localtime. Use UTC by default would confuse a lot of people here. For example current logs from In case, logs are UTC or in winter time Having different times on a single line looks very odd. I agree with you. UTC is removes a lot trouble, for example daylight saving time and helps if operations is done in multiple timezones. In conclusion, the system time should be also UTC. Consider to set
From my point of view, this is the real issue here. Using RFC3339 ( |
dBotLFG
changed the title
|
Agreed, switched to RFC3339 |
2 participants
Issue #, if available:
Description of changes:
Change date formats in logging to use UTC
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.