Kafka, mail # user - Re: anecdotal uptime and service monitoring - 2012-12-28, 22:48
 Search Hadoop and all its subprojects:

Switch to Threaded View
Copy link to this message
-
Re: anecdotal uptime and service monitoring
At LinkedIn, the most common failure of a Kafka broker is when we have to
deploy new Kafka code/config. Otherwise, the broker can be up for a long
time (e..g, months). It woud be good to monitor the following metrics at
the broker: log flush time/rate, produce/fetch requests/messages rate, GC
rate/time, network bandwidth utilization,  and disk space and I/O
utilization. For the clients, it would be good to monitor message
size/rate, request time/rate, dropped event rate (for async producers) and
consumption lag (for consumers). For ZK, ideally, one should monitor ZK
request latency and GCs.

Thanks,

Jun

On Fri, Dec 28, 2012 at 7:27 AM, S Ahmed <[EMAIL PROTECTED]> wrote:
 
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