Configure JMX to provide queue utilization information for ActiveMQ

[robinson]

We installed and configured jmx for splunk to help track java resource utilization in our application. among other things, we want to monitor utilization of ActiveMQ queues. The documentation suggests we can configure config.xml to provide Queue information only out of the activemq package with a stanza like this:

Unfortunately, this results in NO records for the org.apache.activemq domain getting indexed. We successfully index records from the domain in question with this stanza:

However, this results in jmx getting more records indexed into splunk than the rest of my installation combined. This blows my indexing quota. Please help!

[Damien_Dallimor]

You have typos in your MBean declaration.Property keys are case sensitive.

<mbean domain="org.apache.activemq" properties="BrokerName=default,Type=Queue,Destination=*" dumpAllAttributes="true"/>

[Damien_Dallimor]

please accept the answer then.

[robinson]

thanks for that answer. this addressed my issue brilliantly.

[renems]

It seems like you don't get any output at all for your Active MQ queues. That it's not even there while you dump all attributes, is confirming this. Since you don't get any output, it makes sense it isn't indexed in splunk. I suggest posting in the apache forum how to get your activeMQ JMX data first.

[Damien_Dallimor]

see my answer. you have not configured your mbean object name correctly.if you configure the name correctly , you'll get just the information you require without sucking every bit and byte from the parent mbean domain.

[robinson]

thanks for your response, but you have misunderstood the problem. i had hoped it would be clear from my original post that the main issue here is that when i dump all attributes for properties=* i get more data than i can handle, in the sense that my license quota gets exceeded.