Yeah all our monitoring is just of the local process (basically just a
counter exposed through yammer metrics which support jmx and other
outputs). If I understand what you want instead of having a counter that
tracks, say, produce requests per second for a single broker you want one
that covers the whole cluster. Obviously this would require collecting the
local count and aggregating across all the brokers.

Our assumption is that you already have a separate monitoring system which
can slurp all these up, aggregate them, graph them, and alert off them.
There are a number of open source thingies like this and I think most
bigger shops have something they use. Our assumption is that trying to do a
kafka-specific monitoring system wouldn't work for most people because they
are wedded to their current setup and just want to integrate with that.

I'm not sure how valid any of those assumptions actually are.

On Wed, Jul 24, 2013 at 7:29 AM, Otis Gospodnetic <
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB