Backloading events with no year in timestamp

[msorenson]

I have some month old syslog data that I need to load into an indexer, but the timestamp doesn't have the year. Is there a way to force the indexer to leverage the defined month, day and time against the current year? Can this be done through an index time props TIME_FORMAT?

[Takajian]

You can refer to following site.

http://docs.splunk.com/Documentation/Splunk/latest/Data/HowSplunkextractstimestamps

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.

1. 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.

1. If an event doesn't have a time or date, use the timestamp from the most recent previous event of the same source.

2. If no events in a source have a date, look in the source (or file) name (Must have time in the event).

3. For file sources, if no time or date can be identified in the file name, use the modification time on the file.

4. If no other timestamp is found, set the timestamp to the current system time (at the event's index time).

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).