[
https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikael Ståldal updated LOG4J2-1010:
-----------------------------------
Description:
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.
was:
It would be useful to have some logging methods in the Logger interface to set
ThreadContext values for a single log message only.
In an asynchronous environment, using ThreadContext as currently defined is not
so useful since JVM threads might not be coupled to the logical flow of the
application.
Summary: Injectable context properties (was: Possibility to set
ThreadContext values in calls to Logger method)
> Injectable context properties
> -----------------------------
>
> Key: LOG4J2-1010
> URL: https://issues.apache.org/jira/browse/LOG4J2-1010
> Project: Log4j 2
> Issue Type: Improvement
> Components: API
> Affects Versions: 2.2
> Reporter: Mikael Ståldal
> 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
