[
https://issues.apache.org/jira/browse/LOG4J2-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16366594#comment-16366594
]
ASF subversion and git services commented on LOG4J2-2250:
---------------------------------------------------------
Commit 1d55f0f1f9c16c376f4f61b7851f262c1a0f2830 in logging-log4j2's branch
refs/heads/master from rpopma
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=1d55f0f ]
LOG4J2-2250 The internal status logger timestamp format is now configurable
with system property `log4j2.StatusLogger.dateformat`.
(cherry picked from commit 377570d)
> Need ISO8601 timestamp for StatusLogger
> ---------------------------------------
>
> Key: LOG4J2-2250
> URL: https://issues.apache.org/jira/browse/LOG4J2-2250
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.10.0
> Reporter: Atle Tokle
> Assignee: Remko Popma
> Priority: Minor
> Fix For: 2.11.0, 3.0.0
>
>
> We use a log-indexing system that uses the date-format to see where next log
> line begins.
> And have a requirement to standardize on ISO8601 format. But the lines
> written by StatusLogger when Log4j2 has a different format. I would like a
> configuration option that could specify the format. i.e.
> {code:java}
> <configuration verbose="true" status="trace" dateformat="ISO8601" >
> ...
> ...
> </configuration>{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
