ta, GA 30339
> > >
> > > Work Cell 470-455-8346
> > > Personal Cell 678-525-2583
> > > Home Phone: 770-945-3315
> > >
> > >
> > > *From: *Liam Clarke
> > > *Reply-To: *"users@kafka.apache.org"
> > > *Date: *Thur
gt; >
> > Work Cell 470-455-8346
> > Personal Cell 678-525-2583
> > Home Phone: 770-945-3315
> >
> >
> > *From: *Liam Clarke
> > *Reply-To: *"users@kafka.apache.org"
> > *Date: *Thursday, December 19, 2019 at 6:13 PM
> > *To: *&quo
;
>
>
> Work Cell 470-455-8346
>
> Personal Cell 678-525-2583
>
> Home Phone: 770-945-3315
>
>
>
> [image: signature_522277300]
>
>
>
>
>
>
>
> *From: *Liam Clarke
> *Reply-To: *"users@kafka.apache.org"
> *Date: *Thursday, Dec
0339
Work Cell 470-455-8346
Personal Cell 678-525-2583
Home Phone: 770-945-3315
[signature_522277300]
From: Liam Clarke
Reply-To: "users@kafka.apache.org"
Date: Thursday, December 19, 2019 at 6:13 PM
To: "users@kafka.apache.org"
Subject: [EXTERNAL] Re: Health Check
We
We've wired the Prometheus JMX exporter java-agent into our Kafka
processes, we've then set up alerts in Prometheus for several key metrics
to monitor cluster health (under replicated partitions/offline partitions,
request handler avg idle percent to measure load etc.) - and because the
JMX exporte
A simple tcp connection to kafka port (9092) should be enough no?
--
Miguel Silvestre
On Tue, Dec 17, 2019 at 8:33 PM M. Manna wrote:
> Jai,
>
> On Tue, 17 Dec 2019 at 17:33, Jai Nanda Kumar
> wrote:
>
> > Hi,
> >
> > How to perform a health check on a running Kafka server in AWS EC2
> > s
Jai,
On Tue, 17 Dec 2019 at 17:33, Jai Nanda Kumar
wrote:
> Hi,
>
> How to perform a health check on a running Kafka server in AWS EC2
> server.
>
SHouldn't this be part of your liveness probe? Or, are you trying to do
this adhoc (not how folks do it anyway)?
>
> Thanks and Regards,
> A.
