This is because of Kafka consumer's fetch model -- a consumer can completely control how the committed offset moves, even resetting them anywhere.
Under these circumstances, MessagesOutPerSec is meaningless. On Mon, Apr 13, 2020 at 11:38 AM 张祥 <xiangzhang1...@gmail.com> wrote: > Hi, > > I am wondering why there isn't a metric called MessagesOutPerSec in Kafka > JMX metrics to describe how many messages are consumed by clients and > fetched by followers per second since there are already metrics like > MessagesInPerSec, BytesInPerSec and BytesOutPerSec. Thanks. >
