Hi, I don't think that the Kafka Broker exposes the current lag as a metric. It's the reason most of those intermediate tools, like Kafka Exporter, exist. The lag information is available to the client itself, but that is based on the received topic metadata and can be out of date.
Kind regards, Richard Bosch Developer Advocate Axual BV https://axual.com/ On Mon, Aug 15, 2022 at 8:07 PM Kafka Life <lifekafka...@gmail.com> wrote: > Dear Kafka Experts > we need to monitor the consumer lag in kafka clusters 2.5.1 and 2.8.0 > versions of kafka in Grafana. > > 1/ What is the correct path for JMX metrics to evaluate Consumer Lag in > kafka cluster. > > 2/ I had thought it is FetcherLag but it looks like it is not as per the > link below. > > https://www.instaclustr.com/support/documentation/kafka/monitoring-information/fetcher-lag-metrics/#:~:text=Aggregated%20Fetcher%20Consumer%20Lag%20This%20metric%20aggregates%20lag,in%20sync%20with%20partitions%20that%20it%20is%20replicating > . > > Could one of you experts please guide on which JMX i should use for > consumer lag apart from kafka burrow or such intermediate tools > > Thanking you in advance >
