Some events are missing - Time parsed is too far away from the previous event's time

Available Languages

Updated:September 29, 2026
Document ID:SPLK045747

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Applicability

Splunk Enterprise

Description

Splunk received 8 events but the notepad file (data file) having 10 events.

Investigation

In splunkd logs the following warnings were found:

WARN DateParserVerbose - Time parsed (Mon Jul 4 00:00:00 2022) is too far away from the previous event's time (Mon Jul 4 19:20:06 2022) to be accepted. If this is a correct time, MAX_DIFF_SECS_AGO (3600) or MAX_DIFF_SECS_HENCE (604800) may be overly restrictive. Context: source=D:\ConnectHotel\v2240\Log\04Jul2022_.txt|host=VMAWAPP01|AmexProd|260798

WARN DateParserVerbose - Time parsed (Tue Jul 5 10:40:23 2022) is too far away from the previous event's time (Wed Jul 6 00:00:00 2022) to be accepted. If this is a correct time, MAX_DIFF_SECS_AGO (3600) or MAX_DIFF_SECS_HENCE (604800) may be overly restrictive. Context: source=D:\ConnectHotel\v2240\Log\05Jul2022_.txt|host=VMAWAPP01|AmexProd|277173

It means Splunk detected that the timestamps in that data source are further apart than expected. There are a couple possible explanations for that.

2.1: The data really does have timestamps that are far apart. If this is expected then you can ignore the warning or change the MAX_DIFF_SECS_AGO setting in props.conf.
2.2: If you are actually indexing historical data at the same time as current data, then you should ensure that let Splunk know this by using the settings identified in the event MAX_DIFF_SECS_AGO or MAX_DIFF_SECS_AGO


Resolution

Change the MAX_DIFF_SECS_AGO = 155520000 attribute in  local props.conf under [AmexProd] stanza and restart the Splunk.

The default value of MAX_DIFF_SECS_AGO = 3600.


DateParserVerbose message
Propsconf

Revision History

Revision Publish Date Comments
1.0
29-Sep-2026
Initial Release

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products