[
https://issues.apache.org/jira/browse/LOG4J2-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135228#comment-13135228
]
Ralph Goers commented on LOG4J2-53:
-----------------------------------
The EventData object in SLF4J has an event timestamp. I didn't carry this
forward as a fixed field with StructuredDataMessage but it could be added and
honored as a field. It also would be possible to add a TimeStampMessage
interface that can be used to mark messages that contain such a timestamp.
> Better control over timestamp
> -----------------------------
>
> Key: LOG4J2-53
> URL: https://issues.apache.org/jira/browse/LOG4J2-53
> Project: Log4j 2
> Issue Type: New Feature
> Reporter: scott deboy
>
> For apps which require very accurate event times, the timestamp must be
> provided by the app. In log4j 1.2 it is assigned when the event is created,
> which is the time the event is appended. This could be many milliseconds
> after the actual generation of the event. This also gives the app the
> ability to collect event milestones and then choose at the end of the
> processing whether or not to have them sent to an appender and still control
> the timestamp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
