[
https://issues.apache.org/jira/browse/LOG4J2-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14549828#comment-14549828
]
Gary Gregory edited comment on LOG4J2-1015 at 5/19/15 6:04 AM:
---------------------------------------------------------------
I committed tests and an implementation.
BUT: the test/example configuration in
{{log4j-core\src\test\resources\log4j-marker-lookup.yaml}} MUST use
"$$\{marker:}" as opposed to "$$\{marker}" which is not obvious or pretty, it's
just the way variable substitutions work ATM.
Any ideas on changing that?
was (Author: garydgregory):
I committed tests and an implementation.
BUT: the test/example configuration in
{{log4j-core\src\test\resources\log4j-marker-lookup.yaml}} MUST use
"$${marker:}" as opposed to "$${marker}" which is not obvious or pretty, it's
just the way variable substitutions work ATM.
Any ideas on changing that?
> Add a way to route messages based on the %marker in Layout for RoutingAppender
> ------------------------------------------------------------------------------
>
> Key: LOG4J2-1015
> URL: https://issues.apache.org/jira/browse/LOG4J2-1015
> Project: Log4j 2
> Issue Type: New Feature
> Components: Appenders
> Affects Versions: 2.2
> Reporter: Daniel Marcotte
>
> Hi,
> It seems there's no way to route messages based on the Marker in the
> RoutingAppender. The "%marker" is not part of the Layout. When using SLF4J,
> since it's a core feature of the facade, this would help greatly if it was
> possible to route messages based on the Marker.
> Main StackOverFlow question (answered) :
> http://stackoverflow.com/questions/30111754/log4j2-is-there-a-way-to-route-logs-based-on-marker-with-the-routingappender
> Workaround StackOverFlow question (answered) :
> http://stackoverflow.com/questions/30247323/how-to-create-custom-rewritepolicy-in-log4j2
> Thank you
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
