[jira] [Resolved] (LOG4J2-2588) Unable to reinstate old timeMillis timestamp using log4j2.clock property in JSON layout

["Ralph Goers (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LOG4J2-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralph Goers resolved LOG4J2-2588.
---------------------------------
    Fix Version/s: 2.13.2
       Resolution: Fixed

A new option has been added to JsonLayout. If includeTimeMillis is set to true then the timeMillis attribute will be included instead of instant. Please verify and close.

> 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
>            Assignee: Ralph Goers
>            Priority: Minor
>             Fix For: 2.13.2
>
>
> 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)