About indexed field extraction
When Splunk software 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. These fields are stored in the index and become part of the event data.
- Search-time field extraction, which takes place when you search through data. Splunk software creates those fields when compiling search results and does not store them in the index. See About fields in the Knowledge Manager Manual for information about this type of field extraction.
There are two types of indexed fields:
- Default fields, which Splunk software 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, use search-time field extraction for maximum flexibility. Search-time field extraction is easy to modify after you define 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.3.0, 6.3.1, 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.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.5.0, 6.5.1, 6.5.1612 (Splunk Cloud only), 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.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, 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.1.0, 7.1.1, 7.1.2, 7.1.3