Tune timestamp recognition for better indexing performance
To speed up indexing, you can use props.conf to adjust how far ahead into events the Splunk timestamp processor looks, or even turn off the timestamp processor altogether.
For general information on editing
props.conf for timestamps, see Configure timestamp recognition. If you have Splunk Enterprise and need to modify timestamp extraction, perform the configuration on your indexer machines or, if forwarding data, use heavy forwarders and perform the configuration on the machines where the heavy forwarders run. If you have Splunk Cloud and need to modify timestamp extraction, use heavy forwarder and perform the configuration on the machines where the heavy forwarders run.
Adjust timestamp lookahead
Timestamp lookahead determines how far (how many characters) into an event the timestamp processor looks for a timestamp. Adjust how far the timestamp processor looks by setting the
The default number of characters that the timestamp processor looks into an event is 128. You can set
MAX_TIMESTAMP_LOOKAHEAD to a lower value to speed up indexing. You should particularly do this if the timestamps always occur in the first part of the event.
Look for timetamps in the first 20 characters of events coming from source
[source::foo] MAX_TIMESTAMP_LOOKAHEAD = 20 ...
Disable timestamp processor
You can turn off the timestamp processor entirely to improve indexing performance. Turn off timestamp processing for events matching a specified host, source, or sourcetype by setting the
DATETIME_CONFIG attribute to
DATETIME_CONFIG=NONE, Splunk software does not look at the text of the event for the timestamp. Instead, it uses the event "time of receipt"; in other words, the time the event is received from its input. For file-based inputs (such as monitor) this means that the timestamp comes from the modification time of the input file.
You can also increase indexing performance by setting
CURRENT, which assigns the current system time to each event at the time of indexing.
This example turns off timestamp extraction for events that come from the source
[source::foo] DATETIME_CONFIG = NONE ...
NONE disable timestamp identification, so the default event boundary detection (
BREAK_ONLY_BEFORE_DATE = true) might not work as you expect. When you use these settings, specify
SHOULD_LINEMERGE or the
MUST_BREAK_* settings to control event merging.
Specify time zones for timestamps
About indexed field extraction
This documentation applies to the following versions of Splunk Cloud™: 7.0.11, 7.0.13, 7.2.10, 8.0.2003, 8.0.2004, 8.0.2006, 8.0.2007, 8.1.2008