About indexed field extraction
When Splunk Enterprise indexes data, it parses the data stream into a series of events. As part of this process, it adds a number of fields to the event data. These fields include default fields that it adds automatically and any custom fields that you specify.
The process of adding fields to events is known as field extraction. There are two types of field extraction:
- Indexed field extraction, which was described briefly at the start of this topic and which forms the basis for this chapter. Splunk Enterprise stores these fields in the index, and the fields become part of the event data.
- Search-time field extraction, which takes place when you search through data. Splunk Enterprise creates those fields on the fly and does not store them in the index. See "Create search-time field extractions" in the Knowledge Manager manual for information about this type of field extraction.
There are two types of indexed fields:
- Default fields, which Splunk automatically adds to each event. See "About default fields" in this chapter.
- Custom fields, which you specify. See "Create custom fields at index-time" in this manual.
Note: When working with fields, consider that most machine data either does not have structure or has structure that changes constantly. For this type of data, Splunk recommends using search-time field extraction for the purposes of flexibility. Search-time field extraction is trivial to modify within Splunk once you set it.
Tune timestamp recognition for better indexing performance
About default fields (host, source, sourcetype, and more)
This documentation applies to the following versions of Splunk® Enterprise: 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.0.13, 6.0.14, 6.0.15, 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.1.12, 6.1.13, 6.1.14