We do not have the "MessagesOutPerSec" because when returning messages to consumers in the fetch response, we do not decompress the message set if it is compressed, and hence do not really know the number of raw messages out. It can be roughly estimated as 'BytesOut/MessageSize'.
On Fri, Jul 11, 2014 at 10:28 AM, ravi singh <rrs120...@gmail.com> wrote: > Thanks Guozhang!! > Just checked it after publishing few messages , "MessagesInPerSec" exists > for per topic. > > *But why there isnt "MessagesOutPerSec" similar to BytesOutPerSecond ?* > > *Regards,* > *Ravi* > > > On Fri, Jul 11, 2014 at 10:01 PM, Guozhang Wang <wangg...@gmail.com> > wrote: > > > "MessagesInPerSec" also exists per-topic, but the sensor will only be > > created when there are messages produced to the brokers with this topic > > though. > > > > > > On Fri, Jul 11, 2014 at 9:20 AM, ravi singh <rrs120...@gmail.com> wrote: > > > > > Couldn't find it in the documentation though. > > > http://kafka.apache.org/documentation.html#monitoring > > > > > > I need specifically 'MessagesInPerSec' is there any way to deduce it > > from > > > 'BytesIn/OutPerSecond'. > > > > > > > > > > > > On Fri, Jul 11, 2014 at 8:43 PM, Guozhang Wang <wangg...@gmail.com> > > wrote: > > > > > > > There is indeed a per-topic metric for bytes in and bytes out. Should > > be > > > > named as [TopicName]BytesInPerSec, etc. > > > > > > > > Server does monitor bytes out rate whenever it sends any responses to > > > > consumer/producer clients. > > > > > > > > Guozhang > > > > > > > > > > > > > > > > > > > > On Fri, Jul 11, 2014 at 3:38 AM, ravi singh <rrs120...@gmail.com> > > wrote: > > > > > > > > > Hi Kafka Users, > > > > > > > > > > Is it possible to monitor the number of messages in and out for per > > > topic > > > > > on broker side. > > > > > > > > > > Their is a MBean for "AllTopicsMessagesInPerSec" but I couldn't > find > > > > > anything on per topic basis. > > > > > > > > > > Also what does the "Byte out rate" MBean indicates , because as per > > my > > > > > understanding only the consumer maintains the offset based on > message > > > it > > > > > has consumed so nothing actually comes out of broker, all the > > messages > > > > are > > > > > being retained in the broker for specified interval. > > > > > > > > > > -- > > > > > *Regards,* > > > > > *Ravi* > > > > > > > > > > > > > > > > > > > > > -- > > > > -- Guozhang > > > > > > > > > > > > > > > > -- > > > *Regards,* > > > *Ravi* > > > > > > > > > > > -- > > -- Guozhang > > > > > > -- > *Regards,* > *Ravi* > -- -- Guozhang
