Hi Dong, Unfortunately this does not work when there are no messages, but consumers are still running. BytesOutPerSec increases only when the messages are being delivered to the consumer. But you could have a situation when consumer is already at the end of log & noone is going to produce any more messages. In such a case you would be getting fetch requests, and nothing would be sent out.
Trivial to replicate with `kafka-console-consumer.sh --bootstrap-server localhost:9092 --topic idontexist` Best regards, Adam 2018-05-18 18:49 GMT+01:00 Dong Lin <lindon...@gmail.com>: > Hey Adam, > > Thanks for the KIP. We currently already have the per-topic byte-out-rate > (not including replication traffic) with MBean > path kafka.server:name=BytesOutPerSec,type=BrokerTopicMetrics,topic=*. > Though this is not the FetchRequest rate, it seems to address the > motivation of the KIP by telling Kafka cluster operator whether consumers > are actively reading from a topic. Does that address the problem? > > Thanks, > Dong > > > > On Fri, May 18, 2018 at 8:55 AM, Adam Kotwasinski < > adam.kotwasin...@gmail.com> wrote: > >> Hello, >> >> There haven't been many comments regarding this KIP (not surprising as >> the code change is ~10 lines long). Would it be okay to start the >> vote? >> >> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=80452537 >> >> Best regards, >> Adam Kotwasinski >> >> On Wed, May 2, 2018 at 6:49 AM, Adam Kotwasinski < >> adam.kotwasin...@gmail.com >> > wrote: >> >> > Hello, >> > >> > I have created a KIP to add some additional metrics re number of fetch >> > requests made to brokers - >> > https://cwiki.apache.org/confluence/pages/viewpage. >> action?pageId=80452537 >> > >> > Feedback and suggestions are welcome. >> > >> > Best regards, >> > Adam Kotwasinski >> > >>
