Monitor First In, First Out (FIFO) queues
This topic describes how to configure a First In, First Out (FIFO) input by editing the
inputs.conf file on a Splunk Enterprise instance (Splunk Web does not currently support the definition of FIFO inputs.) If you have Splunk Cloud, use a heavy forwarder to read FIFO queues.
Note: Data that you send over FIFO queues does not remain in computer memory and can be an unreliable method for data sources. To ensure data integrity, use the monitor input instead.
Add a FIFO input to inputs.conf
To add a FIFO input, add a stanza for it to inputs.conf in
$SPLUNK_HOME/etc/system/local/ or your own custom application directory in
If you have not worked with configuration files before, read About Configuration Files in the Admin manual before you begin.
This input stanza configures Splunk Enterprise to read from a FIFO queue at the specified path.
[fifo://<path>] <attribute1> = <val1> <attribute2> = <val2> ...
You can use the following attributes with FIFO stanzas:
||The host key/field to a static value for this stanza. The
Sets the host key's initial value. This key is used during parsing and indexing to set the host field. It also uses the host field at search time.
|The IP address or fully qualified domain name of the host where the data originated|
||The index where events from this input will be stored. The
||The sourcetype key/field for events from this input. Explicitly declares the source type for this data, as opposed to letting it be determined automatically. This is important both for searchability and for applying the relevant formatting for this type of data during parsing and indexing.
Sets the sourcetype key's initial value. This value is used during parsing and indexing to set the source type field. It is also the source type field used at search time.
|Splunk software picks a source type based on various aspects of the data. There is no hard-coded default.|
||Sets the source key/field for events from this input. The
Do not override the source field unless absolutely necessary. The input layer provides a more accurate string to aid in problem analysis and investigation, accurately recording the file from which the data was retreived. Consider use of source types, tagging, and search wildcards before overriding this value.
|The input file path.|
||Where the input processor should deposit the events that it reads.
Set to "parsingQueue" to apply
|Defaults to |
Troubleshoot HTTP Event Collector
Monitor changes to your file system
This documentation applies to the following versions of Splunk® Enterprise: 6.3.0, 6.3.2, 6.3.3, 6.3.4, 6.3.5, 6.3.6, 6.3.7, 6.3.8, 6.3.9, 6.3.10, 6.3.11, 6.3.12, 6.3.13, 6.3.14, 6.4.0, 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.4.5, 6.4.6, 6.4.7, 6.4.8, 6.4.9, 6.4.10, 6.4.11, 6.5.0, 6.5.1, 6.5.2, 6.5.3, 6.5.4, 6.5.5, 6.5.6, 6.5.7, 6.5.8, 6.5.9, 6.5.10, 6.6.0, 6.6.1, 6.6.2, 6.6.3, 6.6.4, 6.6.5, 6.6.6, 6.6.7, 6.6.8, 6.6.9, 6.6.10, 6.6.11, 6.6.12, 7.0.1, 6.3.1, 7.0.0, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.0.7, 7.0.8, 7.0.9, 7.0.13, 7.1.0, 7.1.1, 7.1.2, 7.1.3, 7.1.4, 7.1.5, 7.1.6, 7.1.7, 7.1.8, 7.1.9, 7.1.10, 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.2.7, 7.2.8, 7.2.9, 7.2.10, 7.3.0, 7.3.1, 7.3.2, 7.3.3, 7.3.4, 7.3.5, 7.3.6, 7.3.7, 8.0.0, 8.0.1, 8.0.2, 8.0.3, 8.0.4, 8.0.5, 8.0.6, 7.0.10, 7.0.11