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
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!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Observability Simplified: Combining User Experience, Application Performance & ...

Tech Talk Observability Simplified: Combining User Experience, Application Performance & Network ...

Event Series May & June: From Network Visibility to Service Intelligence

Unifying the Network: Moving from Alert Noise to Service Intelligence with Splunk ITSI In today’s hybrid ...