[
https://issues.apache.org/jira/browse/LOG4J2-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14614460#comment-14614460
]
Ralph Goers edited comment on LOG4J2-1074 at 7/6/15 12:16 AM:
--------------------------------------------------------------
Yes. I know Lillith (https://github.com/huxi/lilith) uses the serialized log
event. I am not sure what chainsaw uses. But anyone using the SerializedLayout
is going to impacted by this. If the field is transient then there should be no
problem.
was (Author: [email protected]):
Yes. I know Lillith (https://github.com/huxi/lilith) uses the serialized log
event. I am not sure what chainsaw uses. But anyone using the SerializedLayout
is going to impacted by this.
> 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
>
> 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]
