Splunk Enterprise

How do I fix this : Failed to parse timestamp in first MAX_TIMESTAMP_LOOKAHEAD?

super_saiyan
Communicator

I've deployed below props to  extract the time splunk. There are WARN messages in splunkd logs as follows DateParserVerbose - Failed to parse timestamp in first MAX_TIMESTAMP_LOOKAHEAD (12) characters of event. Defaulting to timestamp of previous event. 

please refer to the below log 

 

Hounsaya     add_user      4               Thu Sep 15 10:09 - 26:39 (60+00:47)
 

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

 

Labels (2)
0 Karma

super_saiyan
Communicator

Hi @richgalloway  Many thanks for your quick response. Below is my props.conf

 

TIME_PREFIX = (Sun|Mon|Tue|Wed|Thu|Fri|Sat)\s
 
TIME_FORMAT = %b %d %H:%M
 
NO_BINARY_CHECK = true
 
SHOULD_LINEMERGE = false
 
0 Karma

richgalloway
SplunkTrust
SplunkTrust

That looks like it should work, but here's an alternative to try:

TIME_PREFIX = \d\s+
TIME_FORMAT = %a %b %d %H:%M
NO_BINARY_CHECK = true
SHOULD_LINEMERGE = false
---
If this reply helps you, Karma would be appreciated.
0 Karma

richgalloway
SplunkTrust
SplunkTrust

Please share the props.conf settings for the sorucetype, especially TIME_PREFIX, TIME_FORMAT, and MAX_TIMESTAMP_LOOKAHEAD.

---
If this reply helps you, Karma would be appreciated.
0 Karma
Get Updates on the Splunk Community!

Splunk Mobile: Your Brand-New Home Screen

Meet Your New Mobile Hub  Hello Splunk Community!  Staying connected to your data—no matter where you are—is ...

Introducing Value Insights (Beta): Understand the Business Impact your organization ...

Real progress on your strategic priorities starts with knowing the business outcomes your teams are delivering ...

Enterprise Security (ES) Essentials 8.3 is Now GA — Smarter Detections, Faster ...

As of today, Enterprise Security (ES) Essentials 8.3 is now generally available, helping SOC teams simplify ...