I was going through the Release note which was updated into Splunk Docs recently.
https://docs.splunk.com/Documentation/Splunk/latest/ReleaseNotes/FixDatetimexml2020?elqTrackId=29cfe97d93df4472a4746e2296a937f9&elq=7cd999a2e77845b6ad79ff165291d6e3&elqaid=25340&elqat=1&elqCampaignId=
It is mentioned that
> Beginning on January 1, 2020, un-patched Splunk platform instances will be unable to recognize timestamps from events where the date contains a two-digit year. This means data that meets this criteria will be indexed with incorrect timestamps.
My Splunk version of Splunk Enterprise is `7.0.2`, I have checked the format of timestamp from some of the sample events which are indexing into my Splunk instances. The timestamp format of the events which are forwarded to Splunk is correct with four-digit of year. But only my Splunk is showing the timestamp of logged events in two-digit of year. Please refer the highlighted part in the screenshot `Splunk_events_timestamp`
Is the existing timestamp format with the events are right or should I need to modify anything to accommodate with the changes effective on January 1st 2020?
[1]: /storage/temp/276647-splunk-events-timestamp.png
↧