Re: Propose a KIP to report "REAL" broker/consumer fetch latency?

Hi Ming This would be a useful metric from a monitoring perspective especially when troubleshooting or diagnosing issues. Are you looking to modify the Admin API for this capability to be added? The metrics for quorum controllers, brokers, replicas and consumers may need to be reported differentl

Propose a KIP to report "REAL" broker/consumer fetch latency?

Hi All, I am thinking about to start a KIP to report "REAL" broker/consumer fetch latency. Before that, I like to collect any idea or suggestions. I created https://issues.apache.org/jira/browse/KAFKA-12713. The fetch latency is an important metric to monitor for the cluster performance.

[jira] [Created] (KAFKA-12713) Report broker/consumer fetch latency more accurately

Ming Liu created KAFKA-12713: Summary: Report broker/consumer fetch latency more accurately Key: KAFKA-12713 URL: https://issues.apache.org/jira/browse/KAFKA-12713 Project: Kafka Issue Type: Bug

Re: [DISCUSS] KIP-725: Streamlining configurations for TimeWindowedDeserializer.

Thanks Sophie, Most of these changes should be there in my PR. I will wait for a couple of days into next week to see if concerns are raised. Thanks! Sagar. On Sat, Apr 24, 2021 at 1:07 AM Sophie Blee-Goldman wrote: > Thanks Sagar, these changes make sense to me. I don't think we need to call