[
https://issues.apache.org/jira/browse/FLINK-16553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17058893#comment-17058893
]
Tarush Grover edited comment on FLINK-16553 at 3/13/20, 4:24 PM:
-----------------------------------------------------------------
[~aljoscha] I will come up with implementation document and share it with all.
was (Author: app-tarush):
[~aljoscha] I will come up with implementation document and share with all.
> Missing KafkaFetcher topic/partition metrics
> --------------------------------------------
>
> Key: FLINK-16553
> URL: https://issues.apache.org/jira/browse/FLINK-16553
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Kafka, Runtime / Metrics
> Reporter: Fabian Paul
> Assignee: Tarush Grover
> Priority: Major
>
> When using the Kafka universal connector, currently not all KafkaFetcher
> metrics
> ([link|https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/clients/consumer/internals/FetcherMetricsRegistry.java])
> which are exposed through the KafkaConsumer are accessible within the Flink
> metrics system.
> Especially, all metrics which are related to topics and partitions are not
> available. The KafkaConsumer internally only registers those metrics after it
> has fetched some records.
> Unfortunately, at the moment Flink only checks the available metrics right
> after the initialization of the KafkaConsumer when no records are polled, yet.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
