Troubleshoot the Splunk Add-on for JBoss

General troubleshooting

For helpful troubleshooting tips that you can apply to all add-ons, see Troubleshoot add-ons in Splunk Add-ons. For additional resources, see Support and resource links for add-ons in Splunk Add-ons.

Splunk restarts after installing or upgrading the Add-on when the JMX addon is not installed

The JBoss Add-on will trigger a Splunk restart in case the Splunk Add-on for JMX is not installed on the same Splunk instance. The jmx_templates.conf file present in JBoss Add-on will trigger the restart if the Splunk Add-on for JMX is not installed. Install it to avoid a restart.

Splunk Add-on for JBoss logs

This add-on has 4 logs that are located at $SPLUNK_HOME/var/log/splunk:

• splunk_ta_jboss_main.log
• splunk_ta_jboss_setup.log
• splunk_ta_jboss_util.log
• splunk_ta_jboss_account_validation.log

To check for errors in the internal logs for this add-on, you can perform this search:

index=_internal source=*ta_jboss*

You can configure the logging verbosity on the Logging page for the add-on. Supported log levels are INFO, DEBUG, and ERROR.

Splunk Add-on for JMX logs

To check for JMX errors, you can perform this search of the Splunk Add-on for JMX internal logs:

index=_internal source=*jmx*