Getting Data In

Splunk is ignoring timestamp and using indexing time

colin_ewen
New Member

I'm running into an issue with Splunk ignoring the timestamp in a specific log and just using current indexing time. Example extract(XXXX and #### replace letters and numbers)

[2011-09-27-04-03-54][XXXX::IA::Actions][####]: BUYER_EMAIL_INVOICES_ADDRESS: []

[2011-09-27-04-03-54][XXXX::IA::Actions][####]: BUYER_LANGUAGE_ID: [25]

[2011-09-27-04-03-54][XXXX::IA::Actions][####]: BUYER_DATE_FORMAT_ID: [1]

Format is %Y-%m-%d-%H-%M-%S

I've attempted the below dateformat to resolve this (there is a backslash escaping the [ below, it's being removed):

TIME_PREFIX = [

TIME_FORMAT = %Y-%m-%d-%H-%M-%S

Unfortunately, no luck, and it's still showing up with the indexing time.

Any help on this? I'm running into a wall.

Tags (1)
0 Karma

_d_
Splunk Employee
Splunk Employee

Colin, try placing a ^ (to indicate the beginning of the line) in front of the backslash escaping your left bracket in TIME_PREFIX.

0 Karma

gkanapathy
Splunk Employee
Splunk Employee

Where exactly did you place these lines of configuration?

0 Karma

colin_ewen
New Member

I've adjusted props.conf on the backend, but it did not work properly. At this point, it now groups them into chunks of 16 lines as a single event and continues to give them the wrong timestamp.

0 Karma

gkanapathy
Splunk Employee
Splunk Employee
0 Karma

colin_ewen
New Member

I added them to the props.conf on the forwarder. Should the props.conf be added to the indexer too, or just the forwarder?

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas

Watch Now Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas     Do you ever feel ...