[
https://issues.apache.org/jira/browse/LOG4J2-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488609#comment-17488609
]
Piotr P. Karwasz commented on LOG4J2-3394:
------------------------------------------
What about introducing a real {{setCompound}} or modifying {{setLevel}} on the
{{LoggerConfig}} component? This would allow a syntax as the one proposed by
Carter in [this
thread|https://github.com/apache/logging-log4j2/pull/735#issuecomment-1026245393].
Basically we would have {{rootLogger.something}} instead of {{rootLogger}} but:
# this will apply to all formats (whether it will be useful or not),
# we could omit the {{name}} property for all other logger configs.
> The 'rootLogger=${sys:root.logger:-INFO,console}' does not work
> ---------------------------------------------------------------
>
> Key: LOG4J2-3394
> URL: https://issues.apache.org/jira/browse/LOG4J2-3394
> Project: Log4j 2
> Issue Type: Bug
> Components: Configuration
> Reporter: Duo Zhang
> Priority: Major
> Attachments: log4j2.err, log4j2.properties
>
>
> Tried the new feature introduced in LOG4J2-3341 in hbase.
> https://github.com/apache/hbase/pull/4096
> I built a tarball and try to start a standalone hbase instance locally, but
> log4j2 failed to load the system properties of rootLogger.
> Will upload the config and error output.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
