[
https://issues.apache.org/jira/browse/LOG4J2-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17092782#comment-17092782
]
Ralph Goers commented on LOG4J2-2831:
-------------------------------------
Is this issue strictly about the Routing Appender? If so, under the Routes
section you will find
{code:java}
The Routes element accepts a single attribute named "pattern". The pattern is
evaluated against all the registered Lookups and the result is used to select a
Route.{code}
If you are meaning this to be more general than you will need to provide a list
of the places that need fixing. Better yet, please provide a pull request.
> Documentation doesn't list all the Appenders that can do runtime lookup
> -----------------------------------------------------------------------
>
> Key: LOG4J2-2831
> URL: https://issues.apache.org/jira/browse/LOG4J2-2831
> Project: Log4j 2
> Issue Type: Improvement
> Components: Documentation
> Reporter: Horacio Mijail Anton Quiles
> Priority: Major
>
> The Appenders documentation page doesn't seem to mention all the cases in
> which lookups/property substitution are applied at runtime.
> For example, the Routing Appender evidently does runtime substitution, as
> mentioned in
> [https://logging.apache.org/log4j/2.x/manual/configuration.html#PropertySubstitution]
> . This page also says "Not all elements support resolving variables at
> runtime. Components that do will specifically call that out in their
> documentation. "
> However this is not called out in
> [https://logging.apache.org/log4j/2.x/manual/appenders.html#RoutingAppender]
> If "their documentation" means some other page, it'd be good to link to it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
