Not sure if this is helpful, Tim. I recently recorded a video that shows the gist of monitoring Kafka with Prometheus: https://www.youtube.com/watch?v=nk3sk1LO7Bo
Cheers, Alex On Sat, Dec 21, 2019 at 12:13 PM Liam Clarke <liam.cla...@adscale.co.nz> wrote: > Nope, it's a third party project: > https://github.com/prometheus/jmx_exporter > > We're using it with an 0.11 cluster. > > On Sat, 21 Dec. 2019, 1:52 am Sullivan, Tim, <tim_sulli...@homedepot.com> > wrote: > > > > > Wonderful, I assume that it is only in the latest release, > > correct? I’m running 1.1.0 so I’m thinking I’d have to upgrade to get the > > benefits? > > > > > > Tim Sullivan > > > > Be Well > > > > > > > > Sr. Software Engineer > > Supply Chain – IT | Data & Analytics > > The Home Depot > > 2250 Newmarket Parkway | Atlanta, GA 30339 > > > > Work Cell 470-455-8346 > > Personal Cell 678-525-2583 > > Home Phone: 770-945-3315 > > > > > > *From: *Liam Clarke <liam.cla...@adscale.co.nz> > > *Reply-To: *"users@kafka.apache.org" <users@kafka.apache.org> > > *Date: *Thursday, December 19, 2019 at 6:13 PM > > *To: *"users@kafka.apache.org" <users@kafka.apache.org> > > *Subject: *[EXTERNAL] Re: Health Check > > > > > > > > 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 exporter runs within the Kafka process, any sustained failure to > scrape > > also sets off an alert. > > > > Cheers, > > > > Liam Clarke > > > > On Thu, Dec 19, 2019 at 12:42 AM Miguel Silvestre <msilves...@gmail.com> > > wrote: > > > > A simple tcp connection to kafka port (9092) should be enough no? > > > > -- > > Miguel Silvestre > >
