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
Get Updates on the Splunk Community!

Building Reliable Asset and Identity Frameworks in Splunk ES

 Accurate asset and identity resolution is the backbone of security operations. Without it, alerts are ...

Cloud Monitoring Console - Unlocking Greater Visibility in SVC Usage Reporting

For Splunk Cloud customers, understanding and optimizing Splunk Virtual Compute (SVC) usage and resource ...

Automatic Discovery Part 3: Practical Use Cases

If you’ve enabled Automatic Discovery in your install of the Splunk Distribution of the OpenTelemetry ...