I have been at this for a couple of days now and it shows I know very little about JMS and/or ActiveMQ. All I want is the stats like size, consumerCount, enqueueCount and dequeueCount for a dashboard panel. I am not getting any errors from the logs and in reality it is returning the messages including the bodies. All I want are the stats--nothing else. The more stats the better. I have been testing this on two of the many queues we have here. The latest version of the inputs.conf (hand written) on each of the ActiveMQ servers returning information via a Universal Forwarder follows;
I am assured it is something simple I am doing wrong. Could someone please point it out? For versions it is Splunk DevTest 6.5.1, Java openjdk version "1.8.0_111", JMS Messaging Modular Input (jms_ta) 1.5.1 and ActiveMQ 5.9.1. Hope I did not forget anything. BTW, there is not a blank line between [jms] and what follows--without the blank line it crunched everything onto one line ???
I was afraid you were going to respond with that. The primary reason I was looking at the jms app was to avoid needing a heavy forwarder to get the information. I ran into that with WebSphere apps and TAs. The Monitoring of Java Virtual Machines with JMX (app 668) app looks like it will fit the bill. Thanks for the quick response and if I find a need to index queues and topics--you do have a great app for that.