[
https://issues.apache.org/jira/browse/LOG4J2-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17049952#comment-17049952
]
ASF subversion and git services commented on LOG4J2-2779:
---------------------------------------------------------
Commit c6c2c0b86c894c71dbf991cea299abbb4f4e011a in logging-log4j2's branch
refs/heads/release-2.x from Ralph Goers
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=c6c2c0b ]
LOG4J2-2779 - Add ContextDataProviders as an alternative to having to implement
a ContextDataInjector.
> Enhance ContextDataInjector to be more flexible
> -----------------------------------------------
>
> Key: LOG4J2-2779
> URL: https://issues.apache.org/jira/browse/LOG4J2-2779
> Project: Log4j 2
> Issue Type: Improvement
> Reporter: Ralph Goers
> Assignee: Ralph Goers
> Priority: Major
>
> ContextDataInjector allows that it be completely replaced by setting a system
> property. But this is very heavyweight just to add new properties to every
> event.
> New Relic has a need to inject trace data into the event and are currently
> using a custom MessageFactory to do it, which has its problems. A better
> approach would be to allow DataIntector providers that are located via
> ServiceLoader and call each one during construction of a LogEvent.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
