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

Edward Sargisson closed LOG4J2-262.
-----------------------------------


Verified and closed.
                
> FlumeAppender should allow interceptors to be specified on embedded agent
> -------------------------------------------------------------------------
>
>                 Key: LOG4J2-262
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-262
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Appenders
>    Affects Versions: 2.0-beta6
>            Reporter: Edward Sargisson
>             Fix For: 2.0-beta7
>
>         Attachments: log4j2-interceptors.diff
>
>
> A Flume agent can be configured to have interceptors. Events are sent to the 
> interceptors which can drop or modify them before passing them on. Currently, 
> the embedded Flume agent does not allow them to be set because it prevents a 
> configuration with any property that starts with sources.
> This is annoying when setting up a configuration to log Flume itself. In our 
> environment we tag log events with the environment, host and component using 
> interceptors. Sending Flume's logs to the same agent causes issues so the 
> logs have to be sent to another agent. While it would be possible to 
> configure that alternative agent to accept incoming events on a separate port 
> per host and component that is a lot of configuration work to maintain.
> The provided patch allows interceptors to be set but continues to disallow 
> other properties that starts with sources. Updated unit tests and a 
> documentation update are also included.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to