Hi all, I'd like to bump up this discussion thread on KIP-736.
I think this would be a useful metric from a monitoring perspective especially when troubleshooting or diagnosing issues. I've tested the fetch latency metric in Twitter's production environment, and provided some examples to illustrate how this metric can be used: https://cwiki.apache.org/confluence/display/KAFKA/KIP-736%3A+Report+the+true+end+to+end+fetch+latency Please give it a look and let me know what you think. Kai On 2021/04/27 18:13:18, Ming Liu <minga...@gmail.com> wrote: > Hi All, I'd like to open up the discussion on a KIP-736. This is to > report the "real" fetch latency by removing the effects of waiting due > to replica.fetch.wait.max.ms or fetch.min.bytes. > > Please give it a look over and let me know what you think. > https://cwiki.apache.org/confluence/display/KAFKA/KIP-736%3A+Report+the+true+end+to+end+fetch+latency > > Thanks >