Getting Data In

DateParserVerbose - Failed to parse timestamp in first MAX_TIMESTAMP_LOOKAHEAD (50) characters of event

firefox95
Explorer

Hi All,

I've deployed below props to splunk SHC and IDX clusters but fields are not extracted in splunk. There are WARN messages in splunkd logs as follows DateParserVerbose - Failed to parse timestamp in first MAX_TIMESTAMP_LOOKAHEAD (50) characters of event. Defaulting to timestamp of previous event (Thu Jan 21 14:02:33 2016). 

Can you please help and let me know if i need to make any changes?

 

[props]

TIME_PREFIX=^

TIME_FORMAT=%d-%b-%Y %I.%M.%S.%6Q %p

MAX_TIMESTAMP_LOOKAHEAD=50

SHOULD_LINEMERGE=false

NO_BINARY_CHECK=true

LINE_BREAKER=([\r\n])\d+\-\w+\-\d+\s+\d+\.\d+\.\d+\.\d+\s+\w+\s

EXTRACT-field1=regex

EXTRACT-field2=regex

 

Sample events:

29-APR-21 09.44.57.234427 AM ,TEST , 11,Login ,2098856,4

29-APR-21 09.44.56.234428 AM ,TEST , 12,Login ,2098856,4

 

Labels (1)
0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

Use lower-case "y" for two-digit years.

TIME_FORMAT=%d-%b-%y %I.%M.%S.%6Q %p
---
If this reply helps you, Karma would be appreciated.

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

Use lower-case "y" for two-digit years.

TIME_FORMAT=%d-%b-%y %I.%M.%S.%6Q %p
---
If this reply helps you, Karma would be appreciated.

firefox95
Explorer

Thank you!! I made changes to Time_Format and corrected MAX_TIMESTAMP_LOOKAHEAD=30 instead of 50 and it worked. 

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