[
https://issues.apache.org/jira/browse/LOG4J2-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465430#comment-17465430
]
ASF subversion and git services commented on LOG4J2-3256:
---------------------------------------------------------
Commit 0cc96b0d65ac589dc90908bc0d4805ee7ad26f1d in logging-log4j2's branch
refs/heads/dependabot/maven/mongodb3.version-3.12.10 from Gary Gregory
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=0cc96b0 ]
[LOG4J2-3256] Reduce ignored package scope of KafkaAppender #640.
Modified GitHub patch #640 from Lee
Dongjin/dongjinleekr/[email protected].
> Reduce ignored package scope of KafkaAppender
> ---------------------------------------------
>
> Key: LOG4J2-3256
> URL: https://issues.apache.org/jira/browse/LOG4J2-3256
> Project: Log4j 2
> Issue Type: Improvement
> Reporter: Dongjin Lee
> Assignee: Gary D. Gregory
> Priority: Major
> Fix For: 2.17.1
>
>
> As of present, KafkaAppender ignores logging messages from the loggers
> starting with "org.apache.kafka". This is because KafkaAppender uses
> KafkaPoducer internally and to avoid recursive logging.
> However, the current ignored package scope, "org.apache.kafka", is too large,
> since KafkaProducer uses "org.apache.kafka.common" and
> "org.apache.kafka.client" only. It is problematic when Apache Kafka uses
> log4j2 for its logging.
> As of present, Apache Kafka is still using log4j 1.x, but a migration project
> is under-progress:
> * KAFKA-9366
> * KAFKA-12399
> If this project is taken, Apache Kafka will deprecate its log4j-appender and
> migrate into log4j2's KafkaAppender. Reducing the ignored package scope is a
> prior task to this work.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
