Getting Data In

DateParserVerbose - Failed to parse timestamp

sharada
Loves-to-Learn Everything

Hi Splunkers,

I am facing the below time stamp issues. Could you please help me with this issue.

08-01-2021 22:49:25.563 -0400 WARN DateParserVerbose - Failed to parse timestamp in first MAX_TIMESTAMP_LOOKAHEAD (800) characters of event. Defaulting to timestamp of previous event (Sun Aug 1 22:49:25 2021).

 

[props]

TIME_FORMAT = %m-%d-%Y%H:%M:%S.%3Q
SHOULD_LINEMERGE = False
is_valid = True
maxDist = 9999
BREAK_ONLY_BEFORE_DATE =
DATETIME_CONFIG = CURRENT
LINE_BREAKER = ([\r\n]+)
MAX_TIMESTAMP_LOOKAHEAD = 800
NO_BINARY_CHECK = true
category = Custom

Labels (2)
0 Karma

venkatasri
SplunkTrust
SplunkTrust

Hi @sharada 

Can you replace with following.

 

[props]
TIME_FORMAT = %m-%d-%Y %H:%M:%S.%3Q
TIME_PREFIX = ^
SHOULD_LINEMERGE = false
LINE_BREAKER = ([\r\n]+)
NO_BINARY_CHECK = true
category = Custom

 

---

An upvote would be appreciated and Accept solution if this reply helps!

 

 

0 Karma

sharada
Loves-to-Learn Everything

Thanks for your response Venkatasri. I modified the props as you suggested but the issue still appears..

0 Karma
Get Updates on the Splunk Community!

Data Management Digest – December 2025

Welcome to the December edition of Data Management Digest! As we continue our journey of data innovation, the ...

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...