[ https://issues.apache.org/jira/browse/KAFKA-10441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17185907#comment-17185907 ]
Pradyumna edited comment on KAFKA-10441 at 8/27/20, 3:12 PM: ------------------------------------------------------------- Do we need to copy the CommonClientConfigs.METRIC_REPORTER_CLASSES_CONFIG from the WorkerConfig to the consumer properties map in this method here? [https://github.com/apache/kafka/blob/2.3/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/Worker.java#L579] so that it get passed into the KafkaConsumer constructor here [https://github.com/apache/kafka/blob/2.3/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/Worker.java#L530] was (Author: pradyumna): Do we need to copy the CommonClientConfigs.METRIC_REPORTER_CLASSES_CONFIG from the WorkerConfig to the consumer properties map in this method here? [https://github.com/apache/kafka/blob/2.3/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/Worker.java#L579] > Connect consumers are missing the fetch metrics > ----------------------------------------------- > > Key: KAFKA-10441 > URL: https://issues.apache.org/jira/browse/KAFKA-10441 > Project: Kafka > Issue Type: Bug > Components: consumer, KafkaConnect > Affects Versions: 2.3.0 > Reporter: Pradyumna > Priority: Minor > > Kafka connect workers create KafkaConsumers and consume from Kafka topics. > > However, unlike regular KafkaConsumers which have a good set of metrics in > the group consumer-fetch-manager-metrics (such as records-lag, > records-consumed-total etc), these KafkaConsumers created by Kafka Connect do > not have any of these consumer metrics. > > I took a heap dump and saw that the "sensors" field in the metrics field of > the KafkaConsumer objects created by Kafka Connect had only the connect > metrics, and not the consumer fetch metrics. > > I tried briefly to find out where in the Kafka code is the metrics object > being reset or the sensors field of the metrics object overridden by kafka > connect, but I could not locate anything yet. -- This message was sent by Atlassian Jira (v8.3.4#803005)