

To discover the processing components, follow these two procedures:Īn instance typically contains at most one processing component. Later, you examine the instances to see if they host management components. For syntax and other details, see Use btool to troubleshoot configurations in the Troubleshooting Manual.įirst, examine each instance to see if it hosts a processing component. The advantage of btool is that it reports back the final set of configurations that results after layering all copies of the file. The btool utility in $SPLUNK_HOME/bin provides a quick way to sift through all copies of a configuration file. To examine a configuration file, you can use either a text editor or the btool utility.Ĭaution: If you use a text editor, do not make any changes to the files. To be certain of your configurations, however, you must examine all possible locations for copies of each relevant file. The files that contain component configurations, such as nf, usually reside only under $SPLUNK_HOME/etc/system/local, because component settings are system-level configurations and should not be app-dependent. To learn how multiple copies of a configuration file layer, see Configuration file precedence in the Admin Manual. If a configuration file has copies in multiple locations, the operative value of each setting in the file is determined by a process of file layering, based on an order of precedence.įor details on configuration file locations, see Configuration file directories in the Admin Manual.
#Splunk conf files how to
This topic describes the elements of Splunk Enterprise deployments and offers essential guidance on how to discover your deployment topology.Ĭopies of configuration files can reside in several locations, including system directories and app directories. The topics in this chapter provide important background information on configuration files: what they are, where they reside, and how they layer on top of one another. The chapter Administer Splunk Enterprise with configuration files in the Admin Manual.It can be helpful to draw a diagram of your deployment, as you go about the discovery process. The discovery process looks for the characteristic configurations of each component type. The settings also help determine the relationships between components, and thus, the overall topology. The files contain settings whose presence or absence help you to determine what component the instance functions as. In this method of discovery, you examine certain configuration files residing on each Splunk Enterprise instance. Examine configuration files to determine your topology
