Getting Data In

DateParserVerbose - Failed to parse timestamp. Defaulting to timestamp of previous event

nathanlhopkins
Path Finder

In my Splunkd log for one of our webspheres I'm finding multiple entries with;

DateParserVerbose - Failed to parse timestamp. Defaulting to timestamp of previous event ...

Please can anyone advise what might be the fix for this?

Do I need to create my own sourcetype? with props.conf?

Tags (2)

DavidLago
New Member

Just insert this line inside your props sourcetype section:

DATETIME_CONFIG = CURRENT
0 Karma

kml_uvce
Builder

your timestamp extraction not working properly, make changes in props.conf http://docs.splunk.com/Documentation/Splunk/latest/Admin/Propsconf

-Kamal Bisht

kamal singh bisht

Michael
Contributor

geez, how I love RTFM answers...

0 Karma

nathanlhopkins
Path Finder

When I use data preview - should I see the issue? Are the green values highlighted the problem or a good match on timestamp?

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!

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Introducing the 2026 - 2027 SplunkTrust cohort!

The goal of the SplunkTrust™ membership has historically been to acknowledge and recognize those who go above ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...