You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Ralph Goers (Jira)" <ji...@apache.org> on 2020/03/03 06:53:00 UTC

[jira] [Resolved] (LOG4J2-2779) Enhance ContextDataInjector to be more flexible

     [ https://issues.apache.org/jira/browse/LOG4J2-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralph Goers resolved LOG4J2-2779.
---------------------------------
    Fix Version/s: 2.13.2
       Resolution: Fixed

> 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
>             Fix For: 2.13.2
>
>
> 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)