Splunk Enterprise

troubleshooting.

whitecat001
Explorer

Am getting a warning of 

  DateParserVerbose - Accepted time (Wed Feb 14 17:01:12 2024) is suspiciously far away from previous event  (Thu jan  18 17:01:12 2024) is still acceptable because it was extracted by the same pattern 

Is there any configuration that can help take this error away in splunk

 

Labels (1)
0 Karma

isoutamo
SplunkTrust
SplunkTrust
Quite possibly there are missing time format on your props.conf. For that reason splunk guess between mm/dd/yyyy and dad/mm/yyyy formats.
0 Karma

richgalloway
SplunkTrust
SplunkTrust

Make sure the props.conf settings for that sourcetype have the correct time settings.  Specifically, check the TIME_PREFIX, TIME_FORMAT, and MAX_TIMESTAMP_LOOKAHEAD values.

Confirm the data source is sending the right events.

---
If this reply helps you, Karma would be appreciated.
0 Karma

whitecat001
Explorer

The first event that came in doesnt have a timestamp which is the reason for the error but the other events are extracted properly

Get Updates on the Splunk Community!

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

Splunk MCP & Agentic AI: Machine Data Without Limits

Discover how the Splunk Model Context Protocol (MCP) Server can revolutionize the way your organization uses ...

Application management with Targeted Application Install for Victoria Experience

Experience a new era of flexibility in managing your Splunk Cloud Platform apps! With Targeted Application ...