Kafka Consumer - JMX Mbean Properties

[Jagadeesh Motamarri]

I enabled JMX on the kafka brokers on port 8081. When I view the MBean properties in jConsole, I only see the following for `kafka.consumer`- 

    kafka.consumer:type=FetchRequestAndResponseMetrics,name=FetchRequestRateAndTimeMs,clientId=ReplicaFetcherThread-2-413

  

    kafka.consumer:type=FetchRequestAndResponseMetrics,name=FetchResponseSize,clientId=ReplicaFetcherThread-0-413

But none of the other ones that are identified here - https://blog.serverdensity.com/how-to-monitor-kafka/ - under Kafka Consumer Metrics are emitted by JMX.

Kafka Version # 0.8.2.1 / 0.9

I am specifically interested in - 

`kafka.consumer:type=ConsumerFetcherManager,name=MaxLag,clientId=([-.\w]+)`

Is there any other way we can capture max lag by consumer via JMX? And more importantly, why are the other properties not emitted by the broker?

Thanks!

[Jagadeesh Motamarri]

Any one?

[Manikumar Reddy]

Are you looking at server mbeans or client mbeans?  MaxLag is client side metric.

Try to monitor the consumer client app.

-Manikumar

--
You received this message because you are subscribed to the Google Groups "kafka-clients" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kafka-client...@googlegroups.com.
To post to this group, send email to kafka-...@googlegroups.com.
Visit this group at https://groups.google.com/group/kafka-clients.
To view this discussion on the web visit https://groups.google.com/d/msgid/kafka-clients/0cca539a-633e-4b73-87f4-e8452a3787e3%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Jagadeesh Motamarri]

Yes, I got it resolved. My consumer client was configured incorrectly with a wrong jmx port.

I see the stats now