You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 30, 2024. It is now read-only.
I would prefer my apps to log in UTC to avoid issues around summer/winter time changes but right now some servers are configured with a non-UTC timezone.
I tried starting up orchestrator with TZ=utc but this does not seem to modify the logging behaviour. It would be good to take this into account or allow me to provide a command line option to request orchestrator log in UTC directly.
Neither of these issues is critical but it might be nice to ensure that logging is consistent and that there is a way that I can force logging to be in UTC even if the system timezone is not UTC. I notice that log.SetFlags from package "log" has a flag LUTC precisely to set logging in UTC.
The text was updated successfully, but these errors were encountered:
I would prefer my apps to log in UTC to avoid issues around summer/winter time changes but right now some servers are configured with a non-UTC timezone.
I tried starting up orchestrator with
TZ=utc
but this does not seem to modify the logging behaviour. It would be good to take this into account or allow me to provide a command line option to request orchestrator log in UTC directly.I also notice that of all the logging most of it uses
"github.com/openark/golib/log"
except one place which uses"log"
directly: https://github.com/github/orchestrator/blob/master/go/raft/file_snapshot.go#L12. This seems somewhat odd as it means logging will not be consistent.Neither of these issues is critical but it might be nice to ensure that logging is consistent and that there is a way that I can force logging to be in UTC even if the system timezone is not UTC. I notice that
log.SetFlags
from package"log"
has a flagLUTC
precisely to set logging in UTC.The text was updated successfully, but these errors were encountered: