[
https://issues.apache.org/jira/browse/LOG4J2-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627373#comment-14627373
]
Remko Popma commented on LOG4J2-1074:
-------------------------------------
AsyncLogger populates RingBufferEvents. This is the disruptor equivalent of
creating new Log4jLogEvents (but event objects are pre-allocated and mutated
instead).
Log4jLogEvents has a Clock to initialize its milliTime field at construction,
and similarly AsyncLogger has a Clock to initialize the RingBufferEvent's
milliTime field before publishing it to the ring buffer.
So having the NanoClock in the same place for the same purpose makes things
consistent. The difference with the NanoClock is that the millis Clock never
changes during the life of the system.
> Add a logformat token for nanotime
> ----------------------------------
>
> Key: LOG4J2-1074
> URL: https://issues.apache.org/jira/browse/LOG4J2-1074
> Project: Log4j 2
> Issue Type: New Feature
> Reporter: Will Hains
> Assignee: Remko Popma
>
> Add a token in the log format specifier to output the current value of
> {{System.nanotime()}}.
> We are currently adding the nanotime value to our log messages manually,
> which we find very useful for troubleshooting unexpected latency, and as a
> quick-and-dirty data source to feed into performance analysis tools.
> It would be very nice if Log4j could do this for us. It would also be nice to
> have this in the log format specified, so we can turn it on/off at runtime by
> editing the Log4j config file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
