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
Currently Tjahzi timestamps all logs using milliseconds precision timer. It is provided by log4j via getTimeMillis method on LogEvent.
Log4j and Loki supports finer precision timestamps. On Log4j side these are available via getInstant method. We should use that instead of getTimeMillis.
Originally posted by thgau August 26, 2022
I use the Thahzi with log4j and I see that the loki timestamp always has 000000 in the micro/nanoseconds part.
log4j is able to give the timestamps with finer resolution. I can put these into the text part. But still it does not reach the loki timestamp.
The text was updated successfully, but these errors were encountered:
* Re 96: Using fine precision event time provided by log4j for log line timestamps. Loki as well as our serializer support it.
* Re #96: Fixed tests.
* Re #96: Fixed tests.
* Re #96: Improved tests.
Currently Tjahzi timestamps all logs using milliseconds precision timer. It is provided by log4j via
getTimeMillis
method onLogEvent
.Log4j and Loki supports finer precision timestamps. On Log4j side these are available via
getInstant
method. We should use that instead ofgetTimeMillis
.Discussed in #95
Originally posted by thgau August 26, 2022
I use the Thahzi with log4j and I see that the loki timestamp always has 000000 in the micro/nanoseconds part.
log4j is able to give the timestamps with finer resolution. I can put these into the text part. But still it does not reach the loki timestamp.
The text was updated successfully, but these errors were encountered: