[
https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15398682#comment-15398682
]
Remko Popma commented on LOG4J2-1010:
-------------------------------------
As Mikael commented
[here|https://issues.apache.org/jira/browse/LOG4J2-1447?focusedCommentId=15395488&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15395488],
{{DynamicThresholdFilter}} filters on context data from the LogEvent once a
log event has been created, and filters on context data from the ThreadContext
directly if a LogEvent has not been created yet. I think what Mikael was trying
to say was that with LOG4J2-1010, we can no longer assume that the
ThreadContext is relevant for all LogEvents. Good point. It is not clear to me
yet how DynamicThresholdFilter should be modified.
> 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-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
