HTTP Event Collector stores its settings on your Splunk server in two .conf files: inputs.conf and outputs.conf. This topic covers HTTP Event Collector-specific settings in these files.
For general information about the inputs.conf and outputs.conf files in their entirety, see the following topics:
This topic contains the following sections:
Settings related to token management are stored in the inputs.conf file. While, in most cases, you edit inputs.conf in the $SPLUNK_HOME/etc/system/local directory, for HTTP Event Collector, you should edit $SPLUNK_HOME/etc/apps/splunk_httpinput/local/inputs.conf. If the local directory doesn't yet exist, create it in the location indicated in the path. If the inputs.conf file doesn't exist, create a new version of the file in the local directory and then modify the values there, but do not directly edit the file in the default directory. No matter how many inputs.conf files a Splunk Enterprise instance has and where they reside, Splunk Enterprise combines all their settings, using the rules of location precedence, as described in "Configuration file precedence".
You can specify whether settings apply globally (to all tokens) or to specific tokens:
The inputs.conf.spec file contains basic explanatory information about each setting. For more detailed information, find the configuration parameter you're looking for here.
The [http] stanza contains global settings that apply to all tokens.
|dedicatedIoThreads||The number of dispatcher threads on the HTTP Event Collector server. The default value is 2. This setting should not be altered unless you have been requested to do so by Splunk Support. The value of this parameter should never be more than the number of physical CPU cores on your Splunk Enterprise server.|
|disabled||Whether tokens are disabled. 1 indicates true; 0 indicates false. The default value is 0. When set to 1 in the [http] stanza, this parameter disables all tokens.|
|enableSSL||Whether the HTTP Event Collector server protocol is HTTP or HTTPS. 1 indicates HTTPS; 0 indicates HTTP. The default value is 1. If you set enableSSL to 1, HTTP Event Collector uses the SSL settings specified in the [general] stanza of the server.conf file.|
|index||The global default index. This parameter can be overridden when set in an individual token's stanza, or by event data whose header contains an index parameter set to a different value. You can limit the set of allowed values for this parameter on a per-token basis by using the indexes parameter.|
|maxSockets||The number of HTTP Event Collector connections (expressed as an integer) that Splunk Enterprise accepts simultaneously. You can limit this number to constrain resource usage. When set to 0, Splunk Enterprise automatically sets it to one third of the maximum allowable open files on the host. If this number is less than 50, it will be set to 50. If this number is greater than 400000, it will be set to 400000. If set to a negative number, no limit will be enforced. Defaults to 0.|
|maxThreads||The number of threads (expressed as an integer) that can be used by active HTTP transactions. You can limit this number to constrain resource usage. When set to 0, Splunk Enterprise automatically sets the limit to one third of the maximum allowable threads on the host. If this number is less than 20, it will be set to 20. If this number is greater than 150000, it will be set to 150000. If maxSockets is not negative and maxThreads is greater than maxSockets, then Splunk Enterprise sets maxThreads to be equal to maxSockets. If set to a negative number, no limit will be enforced. Defaults to 0.|
|outputGroup||The global default output group. An output group is a group of indexers set up by the Splunk Enterprise administrator to index the data. If there is no output group specified, event data will go to the local indexer. If the given output group is invalid, the data will be dropped and an error message will be logged to splunkd.log. For more information about specifying output groups, see Output group-related settings later in this topic.|
|port||The HTTP Event Collector server port. The default value is 8088. This port number must not already be in use.|
|sourcetype||The global default sourcetype. This parameter can be overridden when set in an individual token's stanza, or by event data whose header contains a sourcetype parameter set to a different value.|
|useDeploymentServer||Whether to use Deployment Server. When set to true (1), writes to the location specified by repositoryLocation property in serverclass.conf. Defaults to 0 and writes to $SPLUNK_HOME/etc/apps.|
The [http://<token_name>] stanzas, where <token_name> indicates the token name as assigned by the user, apply to individual tokens. Settings specified here override settings specified within the [http] stanza.
|connection_host||The type of default host for the token. This parameter can be set to any of the following literal values:
|disabled||Whether the token is disabled. 1 indicates true; 0 indicates false. The default value is 0.|
|index||The token's default index. This parameter can be overridden by event data whose header contains an index parameter set to a different value.|
|indexes||A list of allowable indexes to which the data can be indexed.|
|persistentQueueSize||The maximum size of the persistent queue. The value of this parameter is in the form <integer>[KB|MB|GB]. The default value is 0, which indicates there is no persistent queue. Persistent queues can help prevent loss of transient data by saving data in an input queue to disk. When set, the value of the persistentQueueSize parameter must be more than the value of the queueSize parameter. For more information about persistent queues, see Use persistent queues to help prevent data loss.|
|source||The token's default source. This parameter can be overridden by event data whose header contains a source parameter set to a different value.|
|queueSize||The maximum size of the input queue in memory. The value of this parameter is in the form <integer>[KB|MB|GB]. The default value is 500KB.|
|sourcetype||The token's default sourcetype. This parameter can be overridden by event data whose header contains a sourcetype parameter set to a different value.|
|token||The HTTP Event Collector token. The token must be a GUID, and must be unique.|
Settings that apply to forwarding and load balancing are stored in outputs.conf, including settings for specifying HTTP Event Collector output groups. These settings are the same ones that Splunk Enterprise admins use to manage forwarding and load balancing among indexers.
The outputs.conf file contains basic explanatory information about each setting. For more information, see About forwarding and receiving and Configure forwarders with outputs.conf. Following are settings that are relevant to users of HTTP Event Collector.
The [tcpout] stanza defines the output groups to which the data will be forwarded.
|defaultGroup||A comma-separated list of one or more target output group names in the form <target_group>, <target_group>, ... The names of the output groups are specified later in the outputs.conf file in the [tcpout:<target_group>] stanzas. Data will be sent to the specified groups.|
The [tcpout:<target_group>] stanza defines the configuration of the target output group indicated by <target_group>. You can have as many target groups as you want. If more than one target group is specified, the forwarder clones the data to each target group.
|blockWarnThreshold||The output pipeline's send failure count threshold. The default value is 100. After the threshold is met, a failure message will be displayed as a banner in the Splunk Enterprise UI. To effectively disable UI warnings, set this to a very large value (for example, 2000000).|
|server||Required. A comma-separated list of one or more Splunk servers to which to send data. The list is in the form [<ip>|<server name>]:<port>, [<ip>|<servername>]:<port>, ... For each mentioned system, the following are required: