[
https://issues.apache.org/jira/browse/KAFKA-10360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408398#comment-17408398
]
Oleksii Ignachuk commented on KAFKA-10360:
------------------------------------------
This one is pretty tricky when you work with multiple instances of Kafka
clients and create them in runtime since all of them share same static LOCK
object. From performance perspective that's a disaster. Would realy appreciate
if this one would be pushed forward, otherwise we have no other option rather
override kafka classes in our classpath.
The only purpose of this hardcoded reporter is to serve as a source for other
libraries - micrometer + prometheus in our case.
> Disabling JmxReporter registration
> -----------------------------------
>
> Key: KAFKA-10360
> URL: https://issues.apache.org/jira/browse/KAFKA-10360
> Project: Kafka
> Issue Type: New Feature
> Components: clients
> Reporter: Romain Quinio
> Priority: Minor
>
> In Kafka client applications, JMX usage is often being replaced in favor of
> frameworks like micrometer or microprofile-metrics.
> It would be nice to be able to disable the JmxReporter that is today built-in
> with KafkaProducer/KafkaConsumer/KafkaStreams
> [https://github.com/apache/kafka/blob/783a6451f5f8c50dbe151caf5e76b74917690364/clients/src/main/java/org/apache/kafka/clients/producer/KafkaProducer.java#L355-L357]
> [https://github.com/apache/kafka/blob/ffdec02e25bb3be52ee5c06fe76d388303f6ea43/clients/src/main/java/org/apache/kafka/clients/consumer/KafkaConsumer.java#L869-L871]
> [https://github.com/apache/kafka/blob/42f46abb34a2b29993b1a8e6333a400a00227e30/streams/src/main/java/org/apache/kafka/streams/KafkaStreams.java#L685-L687]
> Example of issue in Quarkus: https://github.com/quarkusio/quarkus/issues/9799
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
