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
It seems current log lines add timestamps with second-level precision. In our logging infra this results in thousands of logs sharing the same timestamp which hurts our ability to look at the order of logs. One can drill down on log specific, precise timestamps as infra allows but this loses ordering between log types still.
Open to a PR flipping on precise timestamps? Was this left at the current precision intentionally perhaps?
From what I read logrus accepts go time formats, so setting TimestampFormat to time.RFC3339Nano could be nice, which would provide nanosecond level timestamps.
The text was updated successfully, but these errors were encountered:
alextes
changed the title
Question: why no full timestamp in JSON logs?
Feature request: additional precision for log timestamps
Sep 14, 2023
We could discuss changing the timestamp format to RFC3339Nano! Could you open a PR? Then we can circulate this across the broader boost relay community and ask for input, I don't see a blocker right away.
timestamps may be a bit easier to parse though, not sure if some operators have a strong opinion of timestamp in milliseconds vs RFC3339Nano 🤔 let's start a conversation!
It seems current log lines add timestamps with second-level precision. In our logging infra this results in thousands of logs sharing the same timestamp which hurts our ability to look at the order of logs. One can drill down on log specific, precise timestamps as infra allows but this loses ordering between log types still.
Open to a PR flipping on precise timestamps? Was this left at the current precision intentionally perhaps?
From what I read logrus accepts go
time
formats, so settingTimestampFormat
totime.RFC3339Nano
could be nice, which would provide nanosecond level timestamps.The text was updated successfully, but these errors were encountered: