# Jolokia module for kafka **URL:** \ **Category:** Beats\ **Tags:** metricbeat\ **Created:** [August 29, 2017, 1:53pm UTC](https://discuss.elastic.co/t/jolokia-module-for-kafka/98705 "2017-08-29T13:53:34Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Richard\_Neely](https://avatars.discourse-cdn.com/v4/letter/r/90db22/32.png) [@Richard\_Neely](https://discuss.elastic.co/u/Richard_Neely)\ **Post date:** [August 29, 2017, 1:53pm UTC](https://discuss.elastic.co/t/jolokia-module-for-kafka/98705/1 "2017-08-29T13:53:34Z")
I have setup the jolokia module for kafka but can't seem to get anything to work outside the default jmx mbeans. I know the data is available because i can poll it via other methods but get this for metricbeats. Running 5.5. ``` 2 errors: No key found for metric: 'kafka.server:clientId=Replica,name=MaxLag,type=ReplicaFetcherManager_Value', skipping...; No key found for metric: 'kafka.server:name=UnderReplicatedPartitions,type=ReplicaManager_Value', skipping.. ``` Config: jmx.mappings: - mbean: 'java.lang:type=Runtime' attributes: - attr: Uptime field: uptime - mbean: 'java.lang:type=GarbageCollector,name=ConcurrentMarkSweep' attributes: - attr: CollectionTime field: gc.cms\_collection\_time - attr: CollectionCount field: gc.cms\_collection\_count - mbean: 'java.lang:type=Memory' attributes: - attr: HeapMemoryUsage field: memory.heap\_usage - attr: NonHeapMemoryUsage field: memory.non\_heap\_usage - mbean: 'kafka.server:type=ReplicaFetcherManager,name=MaxLag,clientId=Replica' attributes: - attr: Value field: kafka.server.fetcher.lag.metrics - mbean: 'kafka.server:type=ReplicaManager,name=UnderReplicatedPartitions' attributes: - attr: Value field: kafka.server.under.replicated.partitions: ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 26, 2017, 1:53pm UTC](https://discuss.elastic.co/t/jolokia-module-for-kafka/98705/2 "2017-09-26T13:53:38Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.