<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Timestamp recognition issue in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Timestamp-recognition-issue/m-p/470732#M80915</link>
    <description>&lt;P&gt;I used the "app" method because we have a &lt;CODE&gt;Deployment Server&lt;/CODE&gt;.  It is the easiest way but the &lt;CODE&gt;*.zip&lt;/CODE&gt; download is NOT an app, it is a package of TWO distinct apps that go to TWO separate &lt;CODE&gt;serverclasses&lt;/CODE&gt;.&lt;/P&gt;</description>
    <pubDate>Wed, 18 Dec 2019 20:20:16 GMT</pubDate>
    <dc:creator>woodcock</dc:creator>
    <dc:date>2019-12-18T20:20:16Z</dc:date>
    <item>
      <title>Timestamp recognition issue</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Timestamp-recognition-issue/m-p/470730#M80913</link>
      <description>&lt;P&gt;Dear All,&lt;/P&gt;

&lt;P&gt;We are getting notification of from splunk on time stamp recognition issue from jan 1 2010 it will be effecting the splunk in premise servers as splunk cloud will be taken care by splunk team.&lt;/P&gt;

&lt;P&gt;So i perform below steps will it be fine?&lt;/P&gt;

&lt;P&gt;1) Download the datetime.zip timestamp recognition ZIP file from splunk.com.&lt;BR /&gt;
2) Unarchive the ZIP file to a location that is accessible from all of your Splunk platform instances.&lt;BR /&gt;
On each Splunk platform instance, do the following:&lt;BR /&gt;
Using your operating system file management utilities, copy the updated datetime.xml from the location where you downloaded it to the $SPLUNK_HOME/etc directory on the Splunk platform instance. Ensure that the updated file overwrites the existing file.&lt;BR /&gt;
Confirm that the new datetime.xml has been written to the $SPLUNK_HOME/etc directory.&lt;BR /&gt;
Restart the Splunk platform. Your Splunk platform instance is now patched.&lt;/P&gt;

&lt;P&gt;Because we have to perform on production system so just want a confirmation?&lt;/P&gt;

&lt;P&gt;Regards,&lt;BR /&gt;
Santosh&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 03:27:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Timestamp-recognition-issue/m-p/470730#M80913</guid>
      <dc:creator>santosh11</dc:creator>
      <dc:date>2020-09-30T03:27:28Z</dc:date>
    </item>
    <item>
      <title>Re: Timestamp recognition issue</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Timestamp-recognition-issue/m-p/470731#M80914</link>
      <description>&lt;P&gt;Those are the documented steps.  If you have doubts, you should test them on a non-production system (even if it means installing Splunk on your workstation).&lt;/P&gt;</description>
      <pubDate>Wed, 18 Dec 2019 15:57:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Timestamp-recognition-issue/m-p/470731#M80914</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2019-12-18T15:57:05Z</dc:date>
    </item>
    <item>
      <title>Re: Timestamp recognition issue</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Timestamp-recognition-issue/m-p/470732#M80915</link>
      <description>&lt;P&gt;I used the "app" method because we have a &lt;CODE&gt;Deployment Server&lt;/CODE&gt;.  It is the easiest way but the &lt;CODE&gt;*.zip&lt;/CODE&gt; download is NOT an app, it is a package of TWO distinct apps that go to TWO separate &lt;CODE&gt;serverclasses&lt;/CODE&gt;.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Dec 2019 20:20:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Timestamp-recognition-issue/m-p/470732#M80915</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2019-12-18T20:20:16Z</dc:date>
    </item>
    <item>
      <title>Re: Timestamp recognition issue</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Timestamp-recognition-issue/m-p/470733#M80916</link>
      <description>&lt;P&gt;We have tested this in  our local environment and it is working.&lt;/P&gt;

&lt;P&gt;But in this we have one setting in props.conf&lt;/P&gt;

&lt;P&gt;MAX_DAYS_HENCE = 40&lt;/P&gt;

&lt;P&gt;Is it like from the day it expires it will work only till next 40 days.?&lt;/P&gt;

&lt;P&gt;Can you please explain me about this "Max_DAYS_HENCE" i went through the document can anyone please explain it. I got bit confused and i need to perform these changes into splunk production?&lt;/P&gt;

&lt;P&gt;Regards,&lt;BR /&gt;
Santosh&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 03:27:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Timestamp-recognition-issue/m-p/470733#M80916</guid>
      <dc:creator>santosh11</dc:creator>
      <dc:date>2020-09-30T03:27:44Z</dc:date>
    </item>
    <item>
      <title>Re: Timestamp recognition issue</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Timestamp-recognition-issue/m-p/470734#M80917</link>
      <description>&lt;P&gt;In this context, &lt;CODE&gt;MAX_DAYS_HENCE&lt;/CODE&gt; is used to test the datetime.xml fix.  It can be removed (or returned to the previous value) when testing is complete.&lt;/P&gt;

&lt;P&gt;In general, &lt;CODE&gt;MAX_DAYS_HENCE&lt;/CODE&gt; tells Splunk how to treat timestamps that are newer than today.  Those that are fewer than &lt;CODE&gt;MAX_DAYS_HENCE&lt;/CODE&gt; in the future are accepted; others are not.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Dec 2019 13:51:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Timestamp-recognition-issue/m-p/470734#M80917</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2019-12-19T13:51:32Z</dc:date>
    </item>
  </channel>
</rss>

