[
https://issues.apache.org/jira/browse/LOG4J2-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17042237#comment-17042237
]
Daniel Kirkdorffer commented on LOG4J2-2588:
--------------------------------------------
[~siwyd]Did you ever get a resolution to your issue? We need to do the same.
> Unable to reinstate old timeMillis timestamp using log4j2.clock property in
> JSON layout
> ---------------------------------------------------------------------------------------
>
> Key: LOG4J2-2588
> URL: https://issues.apache.org/jira/browse/LOG4J2-2588
> Project: Log4j 2
> Issue Type: Bug
> Reporter: Simon Wydooghe
> Priority: Minor
>
> As per the changes listed in
> [https://logging.apache.org/log4j/2.0/changes-report.html#a2.11.0,] it seems
> the timestamp is now being reported as
> "instant":\{"epochSecond":1555050778,"nanoOfSecond":738424000} (for instance)
> in the JSON output.
> I'd like to however revert back to the old timeMillis format because it's
> easier to parse using a log forwarder. As per the documentation found, it
> seems I should be able to use log4j2.clock=SystemMillisClock property to
> revert this behaviour. That doesn't seem to work though. I've tried both
> variants of the property I could find in the docs (log4j.Clock and
> log4j2.clock).
> Am I misinterpreting the documentation? I just want an easy way to get back
> the timeMillis.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
