[
https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348005#comment-15348005
]
Mikael Ståldal commented on LOG4J2-1010:
----------------------------------------
OK, let's go for Core, and an interface which adds context properties to a
LogEvent.
A few questions though:
* Do we need to have the configuration properties in this interface? Or should
they be added to the LogEvent always and automatically (as today)?
* How do you register a {{ContextDataInjector}}? As a plugin?
* Should we support having multiple {{ContextDataInjector}}s? Then we can have
a standard one for {{ThreadContext}} which is registered by default.
* In any case I think we should move the handling of {{ThreadContext}} from
{{Log4jLogEvent.createMap()}}, and make it more visible.
> 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
> 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
