I have a few "JVM" Splunk apps in the pipeline that augment the functionality of Splunk for JMX. Tomcat is one such app.
In the interim you can use Splunk for JMX and point it to the "java.lang" and "Catalina" MBean domains, there is a mass of useful JMX attributes and operations to chew over. I'm currently doing this for some large Tomcat deployments.
Here is a simple example config file to get you started.
<jmxpoller>
<!-- custom splunk output formatter-->
<formatter className="com.dtdsoftware.splunk.formatter.TokenizedMBeanNameQuotesStrippedFormatter" />
<cluster name="TomcatInstances" description="All My Tomcat Servers">
<!--
A really simple example, this just discovers and dumps ALL MBean attributes in the "Catalina" and "java.lang" domains
You'll want to figure out what attributes and operations you are specifically interested in and declare them individually.
-->
<mbean domain="Catalina" properties="*" dumpAllAttributes="true" />
<mbean domain="java.lang" properties="*" dumpAllAttributes="true" />
<!--There are many different ways to connect to the JMX server, read the docs.-->
<jmxserver host="host1" jvmDescription="Tomcat1" jmxport="9000"/>
<jmxserver host="host2" jvmDescription="Tomcat2" jmxport="9000"/>
<jmxserver host="host3" jvmDescription="Tomcat3" jmxport="9000"/>
<jmxserver host="host4" jvmDescription="Tomcat4" jmxport="9000"/>
</cluster>
</jmxpoller>
Read the PDF docs first, but feel free to drop me a line if you want any help with a Splunk for JMX config file setup for Tomcat.
answered
06 Oct '11, 15:49
Damien Dalli...
1.2k●1●6
accept rate:
14%