Ensure consistency in logging timestamp formats across all services

[mrzarquon]

Is your feature request related to a problem? Please describe

Diagnosing cross service errors and events is difficult because different services are logging in different timestamp formats. For example, ide-proxy is outputing log settings in epoch time, with server logging in iso 8601 with millesecond precision and Z timezone marker, while most go based services are logging at iso 8601 with second precision and +offset marker.

Anyone having to write a filter to parse all our various logs and create a trace of events across them will need to know each format. Since these are configurable options in the logging libraries used in the services, there should be a consistent option enforced.

Describe the behaviour you'd like

Everyone logs as iso-8601 with MS or NS level precision in UTC

date --iso-8601=ns -u (or date -Ins -u in busybox) generates a timestamp such like 2022-08-05T09:55:13,076934474+0000 and is an option (ms vs ns could be debated) that other logging libraries can match, and can even be defined as a basic log function in our container run commands:

/ # log() { echo "$(date -Ins -u): $*"; }
/ # log hello world
2022-08-05T10:17:39,000000000+00:00: hello world

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[gtsiolis]

Cross-posting #13217 (comment) and follow-up issue #13764 about date format in the dashboard, as this could be helpful for debugging purposes. Cc @mrzarquon

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.