All Apps and Add-ons

Splunk Add-on for Java Management Extensions: Why is the host field not being extracted?

jspears
Communicator

The TA for JMX doesn't seem to be extracting the host field, so all my events appear to come from the heavy forwarder running the add-on. The stanza in transforms is attempting to match on a string starting with host= but I don't see that in any of the data being collected. Here's the stanza included with the app:

 [extract-host]
 DEST_KEY = MetaData:Host
 REGEX = host=([a-zA-Z0-9\._-]+)
 FORMAT = host::$1
0 Karma
1 Solution

jcoates_splunk
Splunk Employee
Splunk Employee

hi, we're setting host to "the instance of the Splunk forwarder that collected the data" and setting source to "the instance of the Java Management Extensions that produced the data", because we may have a 1:many relationship of forwarders and JMX sources.

View solution in original post

jcoates_splunk
Splunk Employee
Splunk Employee

hi, we're setting host to "the instance of the Splunk forwarder that collected the data" and setting source to "the instance of the Java Management Extensions that produced the data", because we may have a 1:many relationship of forwarders and JMX sources.

jspears
Communicator

Thanks. FWIW, this was ultimately rendered moot by running the TA on each UF, connecting to localhost go get the data.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Casting Call: Compete in Cyber Games

Lights, Camera, SecOps: Apply to Compete in Cyber Games     Think you have what it takes to beat the clock? ...

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

How Edge Processor's Durable Queue Works

Edge Processor sits in one of the most consequential places in any Splunk pipeline: between your data sources ...