[
https://issues.apache.org/jira/browse/LOG4J2-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16365808#comment-16365808
]
Remko Popma edited comment on LOG4J2-2250 at 2/15/18 4:16 PM:
--------------------------------------------------------------
@Gary, the status logger is working from startup (much before the configuration
file is loaded). It also works if log4j-core is not used. So a system property
is most appropriate. I agree with Ralph that there should not really be a need
to make this as powerful as the core loggers.
[~atokle], what are you using the status logger output for? This is intended
as a Log4j2 internal diagnostic tool to troubleshoot configuration issues. Once
logging works correctly why are you still capturing the status logger output?
was (Author: [email protected]):
@Gary, the status logger is working from startup (much before the configuration
file is loaded). It also works if log4j-core is not used. So a system property
is most appropriate.
[~atokle], what are you using the status logger output for? This is intended
as a Log4j2 internal diagnostic tool to troubleshoot configuration issues. Once
logging works correctly why are you still capturing the status logger output?
> 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
> Priority: Minor
>
> 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)
