Disable timestamp in logging output #894
Labels
No labels
action
check-aws
action
discussion-needed
action
for-external-contributors
action
for-newcomers
action
more-info-needed
action
need-funding
action
triage-required
kind
correctness
kind
ideas
kind
improvement
kind
performance
kind
testing
kind
usability
kind
wrong-behavior
prio
critical
prio
low
scope
admin-api
scope
background-healing
scope
build
scope
documentation
scope
k8s
scope
layout
scope
metadata
scope
ops
scope
rpc
scope
s3-api
scope
security
scope
telemetry
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#894
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hello, I recognize this is super low priority, but I was wondering if there exists in v1.0.x a way to disable the timestamp which is output as part of the logs? If not, would that be something you would be open to adding?
I run garage using a process manager which already includes the timestamp as part of the logs, so having it again just makes the log line harder to read.
Thanks!
Disable timstamp in logging outputto Disable timestamp in logging outputThis could cause an accuracy issue with your logging manager, as the actual time of the event might be different from the time the log was written to the log file. Out of curiosity, what's the logging manager showing this behavior?
The delay would only the time it takes the process manager to read the line off of stdout/stderr and to re-output it to stdout, which will be microseconds at most. I suppose if garage outputs a ton of logs all at the same time and the process manager gets backed up there could be a discrepancy, but personally I would be ok with that trade-off.
To be clear, I'm suggesting this as an option which can be enabled, not a default behavior.
I would say that virtually every process manager out there prefixes log lines with the timestamp it received them, from systemd to supervisord to docker. For my specific use-case I'm using a custom manager I wrote myself, pmux, which is able to have timestamps prefixed to log lines as an option.