<?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: Few Events indexing with wrong time stamp in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Few-Events-indexing-with-wrong-time-stamp/m-p/305411#M57631</link>
    <description>&lt;P&gt;This happens when you do not tell splunk everything about your timestamps and you allow it to try to figure it out automatically.  You must, at a minimum, use &lt;CODE&gt;TIME_FORMAT&lt;/CODE&gt; (so you are on the right track).  You need to deploy this to your indexers and restart all splunk instances there.  Even so, only events that are indexed after the change will be effected: old broken events will stay broken.&lt;/P&gt;</description>
    <pubDate>Thu, 13 Jul 2017 01:52:59 GMT</pubDate>
    <dc:creator>woodcock</dc:creator>
    <dc:date>2017-07-13T01:52:59Z</dc:date>
    <item>
      <title>Few Events indexing with wrong time stamp</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Few-Events-indexing-with-wrong-time-stamp/m-p/305410#M57630</link>
      <description>&lt;P&gt;I can see that few events for some of the sources are indexing with wrong timestamp(both month and date are swapping), what I mean is events of Jul7th are indexing into Feb 2nd and happens only for few days and again sets back to correct time stamp and vice versa.&lt;/P&gt;

&lt;P&gt;Is there any chance we can fix it and get the wrongly indexed events into correct timestamp back again.&lt;/P&gt;

&lt;P&gt;My events and props.conf(at indexer) is as follows.&lt;/P&gt;

&lt;P&gt;02/07/2017 09:14:40 |....|........&lt;/P&gt;

&lt;P&gt;[sourcetype]&lt;BR /&gt;
disabled=false&lt;BR /&gt;
TIME_FORMAT=%d/%m/%Y %H:%M:%S&lt;/P&gt;

&lt;P&gt;Can anyone help me with this?&lt;/P&gt;</description>
      <pubDate>Thu, 13 Jul 2017 01:37:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Few-Events-indexing-with-wrong-time-stamp/m-p/305410#M57630</guid>
      <dc:creator>rangineniarunku</dc:creator>
      <dc:date>2017-07-13T01:37:15Z</dc:date>
    </item>
    <item>
      <title>Re: Few Events indexing with wrong time stamp</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Few-Events-indexing-with-wrong-time-stamp/m-p/305411#M57631</link>
      <description>&lt;P&gt;This happens when you do not tell splunk everything about your timestamps and you allow it to try to figure it out automatically.  You must, at a minimum, use &lt;CODE&gt;TIME_FORMAT&lt;/CODE&gt; (so you are on the right track).  You need to deploy this to your indexers and restart all splunk instances there.  Even so, only events that are indexed after the change will be effected: old broken events will stay broken.&lt;/P&gt;</description>
      <pubDate>Thu, 13 Jul 2017 01:52:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Few-Events-indexing-with-wrong-time-stamp/m-p/305411#M57631</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2017-07-13T01:52:59Z</dc:date>
    </item>
  </channel>
</rss>

