Metric beat jolokia module cannot read attribute "Value"

Elastic Stack Beats
1

Jolokia agent version: "1.3.6"
METRICBEAT_VERSION=6.0.0-alpha1

I get the following error message while trying to read kafka jmx metric from jolokia
Error:
"message": "1 error: No key found for metric: 'kafka.controller:name=ActiveControllerCount,type=KafkaController_Value', skipping..."

This happens only with attributes called Value. Other attributes like Count work just fine.

 jmx.mappings:
    - mbean: 'kafka.server:name=TotalProduceRequestsPerSec,type=BrokerTopicMetrics'
      attributes:
        - attr: Count
          field: broker.topic.count
    - mbean: 'kafka.server:name=MessagesInPerSec,type=BrokerTopicMetrics'
      attributes:
        - attr: MeanRate
          field: broker.messages_per_sec.meanRate
        - attr: RateUnit
          field: broker.messages_per_sec.rateUnit
    - mbean: 'kafka.controller:type=KafkaController,name=ActiveControllerCount'
      attributes:
        - attr: Value
          field: broker.active_controller.count
2

Update:
Using metricbeat version 6.0.0-alpha2 changes the error message to:
"message": "1 error: metric key '' not found in response"

And the response looks like:

 [jolokia.jmx] The response body from jolokia host 10.61.12.192:8778 is: [  
   {  
      "request":{  
         "mbean":"kafka.server:name=TotalProduceRequestsPerSec,type=BrokerTopicMetrics",
         "attribute":"Count",
         "type":"read"
      },
      "value":{  
         "Count":0
      },
      "timestamp":1499467454,
      "status":200
   },
   {  
      "request":{  
         "mbean":"kafka.controller:name=ActiveControllerCount,type=KafkaController",
         "type":"read"
      },
      "value":{  
         "Value":1
      },
      "timestamp":1499467454,
      "status":200
   }
]
3

One difference I spotted in your config is that for Value you have:

- mbean: 'kafka.controller:type=KafkaController,name=ActiveControllerCount'

But for count you have:

- mbean: 'kafka.server:name=TotalProduceRequestsPerSec,type=BrokerTopicMetrics'

Shouldn't name and type be the other way around?

4

I've tried both configuratoins but that didn't seem to change anything.

Update: That actually worked in alpha2 version. Thanks a lot.

5

Glad do hear it's working.

6

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.