Date Time Assignment to Events Is Extracting Inaccurate Timestamp.

Available Languages

Updated:September 28, 2026

Document ID:SPLK044747

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

When getting the message at _internal "splunkd.log" :

WARN DateParserVerbose - Accepted time (Fri Oct 4 20:37:26 2019) is suspiciously far
away from the previous event's time (Wed Feb 12 21:37:26 2020), but still accepted because 
it was extracted by the same pattern. Context: source="where the data is coming from"

Means that the event time detected and extracted from raw data or _time assigned to the event is suspiciously far away from previous event's time, showing that there's a discrepancy with the actual indextime for the mentioned event and the timestamp extracted.

This may happen due to a mis-configuration at the Heavy Forwarder props.conf file where the data is parsed by a regex defined for the attribute:

TIME_PREFIX = <regular expression>

Resolution

For this scenario is recommended to modify the raw data at the source where the warning message: DateParserVerbose is reporting the mismatch by a format detected by the TIME_FORMAT attribute or modify the TIME_FORMAT with a regex that succesfuly detect the desired data to be extracted.

If this is not possible at all.

- Then a workaround would be to set the attribute

DATETIME_CONFIG = CURRENT

at props.conf in the app or add-on directory where the affected sourcetypes is located in the Heavy Forwarder that parses the event.

This should set the current Heavy Forwarder Time Zone to the event's timestamp.

Note: this workaround will assign the time when the event is ingested as the timestamp for the event.