Replies: 1 comment
-
Hi @insinger. The timestamps were dropped in Litestream logging because it's typically run in something like |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Have you considered including a time/datestamp on any of the messages sent to the console? I've had a case where I can see several lines with messages like "sync error: create generation: initialize shadow wal: read header: EOF", a situation which was eventually resolved by actions taken by the application. But from looking at the console messages I can't tell whether that situation is still active, or when it was resolved. In other words, was the last message written 1 minute ago or 1 day ago? A timestamp would really help in this case.
Similarly, it would be nice to at-a-glance see when the snapshot was written when I see a message "snapshot written 7c04f098aa5bc5b2/00000000". I know I could use the CLI 'snapshots' command to figure this out, but having it right there alongside the message is mighty convenient.
Beta Was this translation helpful? Give feedback.
All reactions