kafka-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Otis Gospodnetić <otis.gospodne...@gmail.com>
Subject Re: Monitoring Kafka client
Date Thu, 08 Sep 2016 05:25:30 GMT
Hi Marius,

I'm curious what you've found?

One way to go about it is to have alerts (those that look for health status
- in SPM we call them Heartbeat alerts) hooked up to a Webhook, where a
Webhook is basically your custom HTTP endpoint (or something like Nagios).
This should let you integrate health status checks into the rest of your
monitoring infra.

Otis
--
Monitoring - Log Management - Alerting - Anomaly Detection
Solr & Elasticsearch Consulting Support Training - http://sematext.com/


On Tue, Sep 6, 2016 at 12:12 AM, Span Marius <mariusspan@gmail.com> wrote:

> Hello Otis,
>
> Thank you for your reply. Sorry for not being very explicit. For this
> particular case, the failed application was on the consumer side, however,
> monitoring the producer in the same way would be desired as well. I had a
> look into SMP. I looks good however I'm up to finding a way to check the
> health status programmatically so that I could integrate this into the my
> existing monitoring infrastructure.
>
> Marius
>
> On Sat, Sep 3, 2016 at 7:23 AM, Otis Gospodnetić <
> otis.gospodnetic@gmail.com
> > wrote:
>
> > Hi,
> >
> > By "kafka client" I assume you mean you Kafka producer and/or consumers?
> > If so, any decent Kafka monitoring solution should let you monitor that.
> > See https://sematext.com/spm/integrations/kafka-monitoring/ for an
> > example.
> >
> > Otis
> > --
> > Monitoring - Log Management - Alerting - Anomaly Detection
> > Solr & Elasticsearch Consulting Support Training - http://sematext.com/
> >
> >
> > On Thu, Sep 1, 2016 at 8:15 AM, Span Marius <mariusspan@gmail.com>
> wrote:
> >
> > > Hi,
> > >
> > > My application recently experience a network connectivity issue which
> > lead
> > > into getting the client (0.8.2.2) disconnected. After the network was
> > > restored the client failed to reconnect because while trying to do
> this,
> > > resolving the Zookeeper Server hostname to an IP failed as well (DNS
> > > failure).
> > >
> > > Is there a reliable way in checking the health status of the client? I
> > > would like to integrate this into the application's healthcheck
> service,
> > > therefore a programmatic approach would fit best.
> > >
> > > Marius Span
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message