<?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 matching outside of the acceptable window in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Timestamp-matching-outside-of-the-acceptable-window/m-p/503442#M85759</link>
    <description>&lt;P&gt;It appears as though Splunk is using a month-day-year time format instead of day-month-year.  To confirm that, please share some sample events (sanitized as necessary) as well as the TIME_FORMAT setting for that sourcetype.&lt;/P&gt;</description>
    <pubDate>Sat, 12 Oct 2019 12:12:23 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2019-10-12T12:12:23Z</dc:date>
    <item>
      <title>Timestamp matching outside of the acceptable window</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Timestamp-matching-outside-of-the-acceptable-window/m-p/503441#M85758</link>
      <description>&lt;P&gt;getting below error after upgrade to latest splunk version:&lt;BR /&gt;
10-11-2019 08:02:49.775 +0000 WARN  DateParserVerbose - The TIME_FORMAT specified is matching timestamps (Sun Nov 10 09:02:47 2019) outside of the acceptable time window. If this timestamp is correct, consider adjusting MAX_DAYS_AGO and MAX_DAYS_HENCE. Context: source=C:\splunk_file\DMVPN Daily Config Backup.txt|host=DTRAFLON2K121|ncm|1584&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 02:36:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Timestamp-matching-outside-of-the-acceptable-window/m-p/503441#M85758</guid>
      <dc:creator>yog123</dc:creator>
      <dc:date>2020-09-30T02:36:12Z</dc:date>
    </item>
    <item>
      <title>Re: Timestamp matching outside of the acceptable window</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Timestamp-matching-outside-of-the-acceptable-window/m-p/503442#M85759</link>
      <description>&lt;P&gt;It appears as though Splunk is using a month-day-year time format instead of day-month-year.  To confirm that, please share some sample events (sanitized as necessary) as well as the TIME_FORMAT setting for that sourcetype.&lt;/P&gt;</description>
      <pubDate>Sat, 12 Oct 2019 12:12:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Timestamp-matching-outside-of-the-acceptable-window/m-p/503442#M85759</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2019-10-12T12:12:23Z</dc:date>
    </item>
    <item>
      <title>Re: Timestamp matching outside of the acceptable window</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Timestamp-matching-outside-of-the-acceptable-window/m-p/503443#M85760</link>
      <description>&lt;P&gt;It is clear to me.  Your event with timestamp &lt;CODE&gt;10-11-2019 08:02:49.775 +0000&lt;/CODE&gt; is being *mis*interpreted as &lt;CODE&gt;Sun Nov 10 09:02:47 2019&lt;/CODE&gt; instead of &lt;CODE&gt;Sat Oct 11 09:02:47 2019&lt;/CODE&gt;.  This is almost always because you are letting Splunk guess at your timestamp instead of TELLING IT yourself.  You need to create a props.conf with these settings:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;TIME_PREFIX = &amp;lt;Your RegEx Here&amp;gt;
TIME_FORMAT = %m-%d-%Y %H:%M:%S.%3N %z
MAX_TIMESTAMP_LOOKAHEAD = 29
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;NEVER let Splunk guess at anything.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 02:31:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Timestamp-matching-outside-of-the-acceptable-window/m-p/503443#M85760</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2020-09-30T02:31:57Z</dc:date>
    </item>
  </channel>
</rss>

