Use the human-friendly zerolog.ConsoleWriter when stdout is a TTY.
This change:
a) moves logging from stderr to stdout (I'm not sure why I used
stderr to begin with)
b) uses a sane time format that abates my hostile OCD operational
tendencies
c) Uses a human-friendly logger when stdout is a TTY. This can be
changed with the flag --json-logs=(true|false) or config value
run.json-logs=(true|false).
d) Uses colorized output when stdout is a TTY. This can be changed
with the flag --use-colors=(true|false) or the config value
run.use-colors=(true|false).
Use the human-friendly zerolog.ConsoleWriter when stdout is a TTY.
This change:
a) moves logging from stderr to stdout (I'm not sure why I used stderr to begin with) b) uses a sane time format that abates my hostile OCD operational tendencies c) Uses a human-friendly logger when stdout is a TTY. This can be changed with the flag
--json-logs=(true|false)
or config valuerun.json-logs=(true|false)
. d) Uses colorized output when stdout is a TTY. This can be changed with the flag--use-colors=(true|false)
or the config valuerun.use-colors=(true|false)
.Human friendly output:
Structured logging:
Fixes: #10