topic Re: Ingest Backdated Files in Splunk Using Event Report Time as Timeline Timestamp in Splunk Enterprise

Ingest Backdated Files in Splunk Using Event Report Time as Timeline Timestamp

LogUx — Mon, 22 Dec 2025 07:33:33 GMT

Hello Splunkers!!

I have a set of backdated files that need to be ingested into Splunk. The requirement is that the event timestamp (report time) should be used as the event time, so that the data appears in the Splunk timeline under the corresponding historical period rather than the current ingestion time.

In the screenshot below, the event report time does not align with the index time. I would like the index time to match the event report time so that the data is accurately reflected in the Splunk timeline.

In my system I am using below setting:
inputs.conf

[monitor://D:\up_ticket_data\tbl_workorder_*.csv]
sourcetype = maximo_workorder
index = maximo_ts
disabled = false
crcSalt = <SOURCE>
#followTail = 0
charset = UTF-8

props.conf
[maximo_workorder]
INDEXED_EXTRACTIONS = csv
LINE_BREAKER = ([\r\n]+)
SHOULD_LINEMERGE = false
FIELD_DELIMITER = ,
FIELD_QUOTE = "
HEADER_FIELD_LINE_NUMBER = 1
CHARSET = UTF-8
TRUNCATE = 999999
TIME_PREFIX = REPORT_DATE,
TIME_FORMAT = %Y-%m-%d
MAX_TIMESTAMP_LOOKAHEAD = 10
TRANSFORMS-drop_header = remove_workorder_csv_header

I need expertise advise to get it fix.

Re: Ingest Backdated Files in Splunk Using Event Report Time as Timeline Timestamp

richgalloway — Mon, 22 Dec 2025 13:06:51 GMT

TIME_PREFIX is the wrong setting to use for CSV files. Use TIMESTAMP_FIELDS, instead.

Also, the TIME_FORMAT setting should be "%Y-%m-%d %H:%M:%S to pick the time as well as the date of the events.

Re: Ingest Backdated Files in Splunk Using Event Report Time as Timeline Timestamp

tscroggins — Mon, 22 Dec 2025 13:39:00 GMT

Hi @LogUx,

Edit: Take @richgalloway's advice. My answer is from the perspective of a single instance. If you're forwarding data, the cooked event from INDEXED_EXTRACTIONS will bypass the receiver's parsing, agg, and typing queues. You can combine the two with force_local_processing on a universal forwarder, but it's not necessary here.

Timestamps are extracted from _raw during aggregation/merging, so you'll want to use a TIME_PREFIX value relative to the event text:

TIME_PREFIX = [+-]\d{2}:\d{2},[^,]+,
MAX_TIMESTAMP_LOOKAHEAD = 25
TIME_FORMAT = %F %T%:z

The default MAX_DAYS_AGO value is 2000, but if your reports are older than that, you'll want to increase that value as well.

If you have a column named "_time" in your CSV file and the value is a Unix epoch time, that value will be the initial value for _time, and a second clean field named "time" without an underscore will be indexed with the original value; however, default timestamp extraction settings will still scan _raw for a timestamp. In your case, 2026-01-16 06:00:00+00:00 would be (or at least should be) extracted absent TIME_PREFIX and TIME_FORMAT settings, overriding any value found by INDEXED_EXTRACTIONS.

Re: Ingest Backdated Files in Splunk Using Event Report Time as Timeline Timestamp

LogUx — Tue, 23 Dec 2025 05:46:29 GMT

Hi @richgalloway After accommodate suggested changes; still my files showing with the same index time in Splunk timeline graph. Is there anything else I need to check or fix /

Re: Ingest Backdated Files in Splunk Using Event Report Time as Timeline Timestamp

richgalloway — Tue, 23 Dec 2025 13:32:04 GMT

It may help to enumerate the data fields rather than have Splunk extract them from the input file. Use the FIELD_NAMES setting to do that. See https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.0/configuration-file-reference/10.0.2-configuration-file-reference/props.conf#:~:text=set)%3A%20not%20set-,FIELD_NAMES,-%3D%20%5B%20%3Cstring%3E%2C...%2C%20%3Cstring%3E%5D%0A*%20Some