<?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: How to limit date timestamp parsing view? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-limit-date-timestamp-parsing-view/m-p/159499#M32361</link>
    <description>&lt;P&gt;You can specify this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;TIME_PREFIX = ^
MAX_TIMESTAMP_LOOKAHEAD = 16
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The prefix tells it where to start, and the lookahead where to stop. Additionally, you could specify an appropriate &lt;CODE&gt;TIME_FORMAT&lt;/CODE&gt;.&lt;/P&gt;</description>
    <pubDate>Mon, 28 Jul 2014 15:06:08 GMT</pubDate>
    <dc:creator>martin_mueller</dc:creator>
    <dc:date>2014-07-28T15:06:08Z</dc:date>
    <item>
      <title>How to limit date timestamp parsing view?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-limit-date-timestamp-parsing-view/m-p/159498#M32360</link>
      <description>&lt;P&gt;I have a proxy server that is double date stamping events.  This is not normally an issue, but I ran into a hydridization of these dates when the 2 date stamps differ:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;  Jul 27 23:59:59 name01 name01.coname.dom: &amp;lt;Mon, 28 Jul 2014 00:00:00,EDT&amp;gt; xxxpayloadxxx
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Splunk date-stamped this event as 7/28/2014 23:59:59.  We are utilizing Splunk's default time stamp parsing for this source.&lt;/P&gt;

&lt;P&gt;I want Splunk to stop looking for a date after 16 characters.  My understanding for the max_timestamp_lookahead in props.conf tells Splunk where to start, not stop.&lt;/P&gt;

&lt;P&gt;Any guidance is appreciated.  Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 17:11:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-limit-date-timestamp-parsing-view/m-p/159498#M32360</guid>
      <dc:creator>gbowden_pheaa</dc:creator>
      <dc:date>2020-09-28T17:11:20Z</dc:date>
    </item>
    <item>
      <title>Re: How to limit date timestamp parsing view?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-limit-date-timestamp-parsing-view/m-p/159499#M32361</link>
      <description>&lt;P&gt;You can specify this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;TIME_PREFIX = ^
MAX_TIMESTAMP_LOOKAHEAD = 16
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The prefix tells it where to start, and the lookahead where to stop. Additionally, you could specify an appropriate &lt;CODE&gt;TIME_FORMAT&lt;/CODE&gt;.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Jul 2014 15:06:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-limit-date-timestamp-parsing-view/m-p/159499#M32361</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-07-28T15:06:08Z</dc:date>
    </item>
    <item>
      <title>Re: How to limit date timestamp parsing view?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-limit-date-timestamp-parsing-view/m-p/159500#M32362</link>
      <description>&lt;P&gt;Awesome - thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 28 Jul 2014 17:36:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-limit-date-timestamp-parsing-view/m-p/159500#M32362</guid>
      <dc:creator>gbowden_pheaa</dc:creator>
      <dc:date>2014-07-28T17:36:20Z</dc:date>
    </item>
  </channel>
</rss>

