How timestamp assignment works
This documentation does not apply to the most recent version of Splunk. Click here for the latest version.
Contents
How timestamp assignment works
Splunk uses timestamps to correlate events by time, create the timeline histogram in Splunk Web and to set time ranges for searches. Timestamps are assigned to events at index time. Most events get a timestamp value assigned to them based on information in the raw event data. If an event doesn't contain timestamp information, Splunk attempts to assign a timestamp value to the event as it's indexed. Splunk stores timestamp values in the _time field (in UTC time format).
Timestamp processing is one of the key steps in event processing. For more information on event processing, see Configure event processing.
Considerations when adding new data
If your data turns out to require timestamp configuration beyond what Splunk does automatically, you must re-index that data once you've configured its timestamp extraction. It's a good idea to test a new data input in a "sandbox" Splunk instance (or just a separate index) before adding it to your production Splunk instance in case you have to clean it out and re-index it a few times to get it just right.
Precedence rules for timestamp assignment
Splunk uses the following precedence to assign timestamps to events:
1. Look for a time or date in the event itself using an explicit TIME_FORMAT if provided.
Use positional timestamp extraction for events that have more than one timestamp value in the raw data.
2. If no TIME_FORMAT is provided, or no match is found, attempt to automatically identify a time or date in the event itself.
Use positional timestamp extraction for events that have more than one timestamp value in the raw data.
3. If an event doesn't have a time or date, use the timestamp from the most recent previous event of the same source.
4. If no events in a source have a date, look in the source (or file) name (Must have time in the event).
5. For file sources, if no time or date can be identified in the file name, use the modification time on the file.
6. If no other timestamp is found, set the timestamp to the current system time (at the event's index time).
Configure timestamps
Most events don't require any special timestamp handling. For some sources and distributed deployments, you may have to configure timestamp formatting to extract timestamps from events. Configure Splunk's timestamp extraction processor by editing props.conf. For a complete discussion of the timestamp configurations available in props.conf, see Configure timestamp recognition.
You can also configure Splunk's timestamp extraction processor to:
- Apply timezone offsets.
- Pull the correct timestamp from events with more than one timestamp.
- Improve indexing performance.
This documentation applies to the following versions of Splunk: 4.1 , 4.1.1 , 4.1.2 , 4.1.3 , 4.1.4 , 4.1.5 , 4.1.6 , 4.1.7 , 4.1.8 View the Article History for its revisions.