Use btool to troubleshoot configurations
The Splunk Enterprise configuration file system supports many overlapping configuration files in many different locations. How these configuration files interact with and take precedence over one another is described in "Configuration file precedence" in the Admin Manual. This flexibility can occasionally make it hard to figure out exactly which configuration value Splunk Enterprise is using.
To help you out, Splunk provides
btool. This is a command line tool that can help you troubleshoot configuration file issues or just see what values are being used by your Splunk Enterprise installation.
Btool displays merged on-disk configurations. To view in-memory configurations, query the REST endpoint /services/properties/
btool is not tested by Splunk and is not officially supported or guaranteed. That said, it's what our Support team uses when trying to troubleshoot your issues.
Investigate configuration values of your entire Splunk installation
You can run
btool to see all the configuration values in use by your Splunk instance.
./splunk cmd btool <conf_file_prefix> list
<conf_file_prefix> is the name of the configuration file you're interested in (minus the
.conf extension). The
list literal specifies that you want to list the options.
For example, to see what settings transforms.conf is using, type:
./splunk cmd btool transforms list
You probably want to send the results of btool into a text file that you can peruse then delete, like this:
./splunk cmd btool transforms list > /tmp/transformsconfigs.txt
or if not to a file, at least pipe to grep like this:
./splunk cmd btool server list --debug | grep '\['
which determines which server.conf stanzas are being recognized.
Piping to a file is handy for all use cases of btool, but for simplicity we'll only explicitly mention it this once.
Investigate configuration values in one app
You can also run
btool for a specific app in your Splunk installation. It will list all the configuration values in use by that app for a given configuration file.
btool, go to
$SPLUNK_HOME/bin and type:
./splunk cmd btool --app=<app_name> <conf_file_prefix> list
<app_name> is the name of the app you want to see the configurations for.
For example, if you want to know what configuration options are being used in
props.conf by the Search app, type:
./splunk cmd btool --app=search props list
This returns a list of the
props.conf settings currently being used for the Search app.
The app name is not required. In fact, it's often a good idea not to specify the app when using
btool. In the case of
btool, insight into all of your configurations can be helpful.
Learn where configuration values come from
Another thing you can do with
btool is find out from which specific app Splunk is pulling its configuration parameters for a given configuration file. To do this, add the
--debug flag to
btool like in this example for props.conf:
./splunk cmd btool props list --debug
btool syntax in "Command line tools for use with Support".
Watch a video on using btool to troubleshoot configuration issues by a Splunk Support engineer.
Have questions? Visit Splunk Answers and see what questions and answers the Splunk community has using btool.
Determine which version of Splunk Enterprise you're running
Splunk on Splunk app
This documentation applies to the following versions of Splunk® Enterprise: 4.3, 4.3.1, 4.3.2, 4.3.3, 4.3.4, 4.3.5, 4.3.6, 4.3.7, 5.0, 5.0.1, 5.0.2, 5.0.3, 5.0.4, 5.0.5, 5.0.6, 5.0.7, 5.0.8, 5.0.9, 5.0.10, 5.0.11, 5.0.12, 5.0.13, 5.0.14, 5.0.15, 5.0.16, 6.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.0.5, 6.0.6, 6.0.7, 6.0.8, 6.0.9, 6.0.10, 6.0.11, 6.0.12, 6.1, 6.1.1, 6.1.2, 6.1.3, 6.1.4, 6.1.5, 6.1.6, 6.1.7, 6.1.8, 6.1.9, 6.1.10, 6.1.11, 6.2.0, 6.2.1, 6.2.2, 6.2.3, 6.2.4, 6.2.5, 6.2.6, 6.2.7, 6.2.8, 6.2.9, 6.2.10, 6.2.11, 6.3.0, 6.3.1, 6.3.2, 6.3.3, 6.3.4, 6.3.5, 6.3.6, 6.4.0, 6.4.1, 6.4.2, 6.4.3