Splunk Enterprise

DateParserVerbose Failed to parse timestamp in first MAX_TIMESTAMP_LOOKAHEAD

hketer
Path Finder

 

Hi,

We have event with time field  Time=1650461136000
Props configuration parsing the time into 
_time: 2022-04-20 16:25:36
_indextime: 04/20/2022 16:22:43

[props]

TIME_PREFIX = ,\Time\=
TIME_FORMAT = %s%3N

That means the data ingest with future time.

With that being said, what are we missing? 
Why we still receive the warning  
"WARN Date ParserVerbose - Failed to parse timestamp in first MAX_TIMESTAMP_LOOKAHEAD (350) characters of event. Defaulting to timestamp of previous event"

Thank you!

 

Labels (2)
Tags (1)
0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @hketer,

I suppose that you already checked the clocks of all the systems and that they are all aligned with an NTP server.

Then, could you share a sample of your logs with the wrong timestamp?

Ciao.

Giuseppe

0 Karma

hketer
Path Finder

Hi,

Thank you for the replay.

The Epochtime is the same as the _time
unfortunately I can't share the raw event.

 

 

0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @hketer,

sorry but I asked a different question: did you checked that the clock of the target server and the one of Indexers are aligned with an NTP server?

It seems that there a different time between them.

If you can't share events I cannot check the timestamp extraction, mask you data before sharing it.

Ciao.

Giuseppe

0 Karma
Get Updates on the Splunk Community!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics GA in US-AWS!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...