logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Goers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-1010) Injectable context properties
Date Fri, 29 Jul 2016 15:25:21 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15399501#comment-15399501
] 

Ralph Goers commented on LOG4J2-1010:
-------------------------------------

As you stated, when a LogEvent has not been created a Filter must filter on the raw data -
so filters that use ThreadContext data must get it from the thread context for those methods.
When the LogEvent is available Filters must get their data from the LogEvent instead and should
never go against the ThreadContext.  The same thing is true with Lookups - when a LogEvent
is available the data must come from there.

> Injectable context properties
> -----------------------------
>
>                 Key: LOG4J2-1010
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1010
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.2
>            Reporter: Mikael Ståldal
>            Assignee: Remko Popma
>             Fix For: 2.7
>
>         Attachments: properties.patch
>
>
> It would be useful to have a way to inject context properties into a {{LogEvent}}, as
an alternative to {{ThreadContext}}.
> In an asynchronous environment, using ThreadContext as currently implemented is not so
useful since JVM threads might not be coupled to the logical flow of the application.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message