PR #104265 - util/log: timezone support for formats crdb-v1 and crdb-v2 (1 of 3)

[cockroach-teamcity]

Exalate commented:

Related PR: cockroachdb/cockroach#104265
Commit: cockroachdb/cockroach@d756dec
Fixes: CRDB-5594 CRDB-19901

---

Release note (cli change): The log output formats crdb-v1 and
crdb-v2 now support the format option timezone. When specified,
the corresponding time zone is used to produce the timestamp column.

For example:

file-defaults:
   format: crdb-v2
   format-options: {timezone: america/new_york}

Example logging output:

I230606 12:43:01.553407-040000 1 1@cli/start.go:575 ⋮ [n?] 4  soft memory limit of Go runtime is set to 35 GiB
                       ^^^^^^^ indicates GMT-4 was used.

The timezone offset is also always included in the format if it is not
zero (e.g. for non-UTC time zones). This is necessary to ensure that
the times can be read back precisely.

Jira Issue: DOC-8104

[exalate-issue-sync]

Florence Morris (florence-crl) commented:
{noformat}I231031 14:30:55.080259+000000 1 1@cli/log_flags.go:200 ⋮ [n?] 1 using explicit logging configuration:
I231031 14:30:55.080259+000000 1 1@cli/log_flags.go:200 ⋮ [n?] 1 +‹file-defaults:›
I231031 14:30:55.080259+000000 1 1@cli/log_flags.go:200 ⋮ [n?] 1 +‹ format: crdb-v2›
I231031 14:30:55.080259+000000 1 1@cli/log_flags.go:200 ⋮ [n?] 1 +‹ format-options: {timezone: etc/utc}›{noformat}

The timezone offset of zero is included if the timezone {{etc/utc}} is specified.