You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "scott deboy (Created) (JIRA)" <ji...@apache.org> on 2011/10/25 18:48:32 UTC
[jira] [Created] (LOG4J2-53) Better control over 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
[jira] [Resolved] (LOG4J2-53) Better control over timestamp
Posted by "Ralph Goers (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOG4J2-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers resolved LOG4J2-53.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.0-alpha1
Assignee: Ralph Goers
TimestampMessage should address this.
> 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
> Assignee: Ralph Goers
> Fix For: 2.0-alpha1
>
>
> 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
[jira] [Commented] (LOG4J2-53) Better control over timestamp
Posted by "Ralph Goers (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOG4J2-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13138131#comment-13138131 ]
Ralph Goers commented on LOG4J2-53:
-----------------------------------
I've added the TimestampMessage interface to the experimental Log4j 2.0. The timestamp in the message will be used.
> 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
[jira] [Closed] (LOG4J2-53) Better control over timestamp
Posted by "Ralph Goers (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOG4J2-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers closed LOG4J2-53.
-----------------------------
Closing since there have been no other comments since this was marked resolved.
> 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
> Assignee: Ralph Goers
> Fix For: 2.0-alpha1
>
>
> 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
[jira] [Commented] (LOG4J2-53) Better control over timestamp
Posted by "Ralph Goers (Commented) (JIRA)" <ji...@apache.org>.
[ 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org