<?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: Incorrect Timestamp in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Incorrect-Timestamp/m-p/238124#M46258</link>
    <description>&lt;P&gt;Your &lt;CODE&gt;TIME_FORMAT&lt;/CODE&gt; should be &lt;CODE&gt;%m-%d-%Y %H:%M:%S.%3N&lt;/CODE&gt;, possibly plus timezone info if the &lt;CODE&gt;+00&lt;/CODE&gt; refers to UTC.&lt;BR /&gt;
After setting that, make sure you restart Splunk and only look at newly indexed events - existing ones won't change.&lt;/P&gt;</description>
    <pubDate>Tue, 08 Mar 2016 21:48:18 GMT</pubDate>
    <dc:creator>martin_mueller</dc:creator>
    <dc:date>2016-03-08T21:48:18Z</dc:date>
    <item>
      <title>Incorrect Timestamp</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Incorrect-Timestamp/m-p/238123#M46257</link>
      <description>&lt;P&gt;I have the following log and need splunk to grab the second timestamp instead of the first.  I have tried adjusting props.conf as shown below as well.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Task Update Application Available Targeting is due at Wednesday 03/09/2016 00:00:00  $$&amp;lt;SMS_DATABASE_NOTIFICATION_MONITOR&amp;gt;&amp;lt;03-08-2016 19:00:26.917+00&amp;gt;&amp;lt;thread=6760 (0x1A68)&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Props.conf&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[server_log]
TIME_PREFIX = &amp;gt;&amp;lt;
TIME_FORMAT = %m-%d-%y %H:%M:%S.
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 08 Mar 2016 21:44:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Incorrect-Timestamp/m-p/238123#M46257</guid>
      <dc:creator>hlarimer</dc:creator>
      <dc:date>2016-03-08T21:44:24Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect Timestamp</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Incorrect-Timestamp/m-p/238124#M46258</link>
      <description>&lt;P&gt;Your &lt;CODE&gt;TIME_FORMAT&lt;/CODE&gt; should be &lt;CODE&gt;%m-%d-%Y %H:%M:%S.%3N&lt;/CODE&gt;, possibly plus timezone info if the &lt;CODE&gt;+00&lt;/CODE&gt; refers to UTC.&lt;BR /&gt;
After setting that, make sure you restart Splunk and only look at newly indexed events - existing ones won't change.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Mar 2016 21:48:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Incorrect-Timestamp/m-p/238124#M46258</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2016-03-08T21:48:18Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect Timestamp</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Incorrect-Timestamp/m-p/238125#M46259</link>
      <description>&lt;P&gt;Thanks Martin, I added those changes but I'm still getting the first timestamp instead of the second.  I added the changes last night and then restarted the splunk forwarder.  Do you think the TIME_PREFIX is correctly?&lt;/P&gt;</description>
      <pubDate>Wed, 09 Mar 2016 13:46:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Incorrect-Timestamp/m-p/238125#M46259</guid>
      <dc:creator>hlarimer</dc:creator>
      <dc:date>2016-03-09T13:46:55Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect Timestamp</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Incorrect-Timestamp/m-p/238126#M46260</link>
      <description>&lt;P&gt;Setting those two things works for me:&lt;/P&gt;

&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="alt text"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/1114iB357D40A3A1ACAF6/image-size/large?v=v2&amp;amp;px=999" role="button" title="alt text" alt="alt text" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 09 Mar 2016 20:07:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Incorrect-Timestamp/m-p/238126#M46260</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2016-03-09T20:07:53Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect Timestamp</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Incorrect-Timestamp/m-p/238127#M46261</link>
      <description>&lt;P&gt;Maybe I have this set in the incorrect place then, I have it in props.conf on the UF, should it actually be on the SH?&lt;/P&gt;</description>
      <pubDate>Wed, 09 Mar 2016 20:33:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Incorrect-Timestamp/m-p/238127#M46261</guid>
      <dc:creator>hlarimer</dc:creator>
      <dc:date>2016-03-09T20:33:34Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect Timestamp</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Incorrect-Timestamp/m-p/238128#M46262</link>
      <description>&lt;P&gt;It should be on the instance that performs the parsing: &lt;A href="http://wiki.splunk.com/Community:HowIndexingWorks"&gt;http://wiki.splunk.com/Community:HowIndexingWorks&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Usually that's the indexers, sometimes heavy forwarders, only very rarely (e.g. INDEXED_EXTRACTIONS) universal forwarders, also rarely search heads (e.g. combined search head with DB Connect, modular inputs, etc).&lt;/P&gt;</description>
      <pubDate>Wed, 09 Mar 2016 20:39:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Incorrect-Timestamp/m-p/238128#M46262</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2016-03-09T20:39:32Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect Timestamp</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Incorrect-Timestamp/m-p/238129#M46263</link>
      <description>&lt;P&gt;Thanks Martin, it looks like moving it to indexers took care of it! That was my mistake, I was thinking that timestamp extraction happened earlier.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Mar 2016 14:03:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Incorrect-Timestamp/m-p/238129#M46263</guid>
      <dc:creator>hlarimer</dc:creator>
      <dc:date>2016-03-10T14:03:25Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect Timestamp</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Incorrect-Timestamp/m-p/238130#M46264</link>
      <description>&lt;P&gt;Great - don't forget to mark the answer as accepted.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Mar 2016 19:33:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Incorrect-Timestamp/m-p/238130#M46264</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2016-03-10T19:33:37Z</dc:date>
    </item>
  </channel>
</rss>

