[
https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15346594#comment-15346594
]
Mikael Ståldal commented on LOG4J2-1010:
----------------------------------------
I think this is putting the abstraction level wrong. I am interested in
providing the context properties, not putting them into the LogEvent.
I would prefer an interface like this:
{code}
/**
* Provide context data for a LogEvent.
* By default context data is obtained from the ThreadContext but implementers
are free to do something different.
*
* @return context data to add to the LogEvent
*/
interface ContextDataInjector {
List<Property> injectContextData();
}
{code}
> 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: [email protected]
For additional commands, e-mail: [email protected]
