Relying on just the TCP connection getting established seems a bit poor, the easiest non-intrusive approach is probably to query the broker for metadata, e.g.: kafkacat -b mybroker -L
2015-02-10 1:47 GMT+01:00 Koert Kuipers <ko...@tresata.com>: > a simple nagios check_tcp works fine. as gwen indicated kafka closes the > connection on me, but this is (supposedly) harmless. i see in server logs: > [2015-02-09 19:39:17,069] INFO Closing socket connection to /192.168.1.31. > (kafka.network.Processor) > > > On Mon, Feb 9, 2015 at 6:06 PM, Scott Clasen <sc...@heroku.com> wrote: > > > I have used nagios in this manner with kafaka before and worked fine. > > > > On Mon, Feb 9, 2015 at 2:48 PM, Koert Kuipers <ko...@tresata.com> wrote: > > > > > i would like to be able to ping kafka servers from nagios to confirm > they > > > are alive. since kafka servers dont run a http server (web ui) i am not > > > sure how to do this. > > > > > > is it safe to establish a "test" tcp connection (so connect and > > immediately > > > disconnect using telnet or netstat or something like that) to the kafka > > > server on port 9092 to confirm its alive? > > > > > > thanks > > > > > >
