<?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 parsing issue  for a specific time in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/timestamp-parsing-issue-for-a-specific-time/m-p/315182#M94360</link>
    <description>&lt;P&gt;The length of the timestamp is 23 characters, not 30, so you need:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;MAX_TIMESTAMP_LOOKAHEAD = 23
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Thu, 23 Feb 2017 07:28:03 GMT</pubDate>
    <dc:creator>woodcock</dc:creator>
    <dc:date>2017-02-23T07:28:03Z</dc:date>
    <item>
      <title>timestamp parsing issue  for a specific time</title>
      <link>https://community.splunk.com/t5/Splunk-Search/timestamp-parsing-issue-for-a-specific-time/m-p/315180#M94358</link>
      <description>&lt;P&gt;my log is:&lt;/P&gt;

&lt;P&gt;2016-12-22 00:01:11,076 [myid:123] - INFO  [xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx] - Accepted data from&lt;/P&gt;

&lt;P&gt;in the props:&lt;/P&gt;

&lt;P&gt;TIME_PREFIX = ^&lt;BR /&gt;
MAX_TIMESTAMP_LOOKAHEAD = 30&lt;BR /&gt;
TIME_FORMAT = %Y-%m-%d %H:%M:%S,%3N&lt;/P&gt;

&lt;P&gt;but i am still getting  this error " failed to parse the timestamp" . after increasing  the lookahead value , this error was disappeared for some time and it started to come back again. can anyone please help me to  figure out what might be the issue .&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 12:57:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/timestamp-parsing-issue-for-a-specific-time/m-p/315180#M94358</guid>
      <dc:creator>kteng2024</dc:creator>
      <dc:date>2020-09-29T12:57:45Z</dc:date>
    </item>
    <item>
      <title>Re: timestamp parsing issue  for a specific time</title>
      <link>https://community.splunk.com/t5/Splunk-Search/timestamp-parsing-issue-for-a-specific-time/m-p/315181#M94359</link>
      <description>&lt;P&gt;MAX_TIMESTAMP_LOOKAHEAD value should be 23, length of timestamp.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 12:57:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/timestamp-parsing-issue-for-a-specific-time/m-p/315181#M94359</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2020-09-29T12:57:48Z</dc:date>
    </item>
    <item>
      <title>Re: timestamp parsing issue  for a specific time</title>
      <link>https://community.splunk.com/t5/Splunk-Search/timestamp-parsing-issue-for-a-specific-time/m-p/315182#M94360</link>
      <description>&lt;P&gt;The length of the timestamp is 23 characters, not 30, so you need:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;MAX_TIMESTAMP_LOOKAHEAD = 23
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 23 Feb 2017 07:28:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/timestamp-parsing-issue-for-a-specific-time/m-p/315182#M94360</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2017-02-23T07:28:03Z</dc:date>
    </item>
    <item>
      <title>Re: timestamp parsing issue  for a specific time</title>
      <link>https://community.splunk.com/t5/Splunk-Search/timestamp-parsing-issue-for-a-specific-time/m-p/315183#M94361</link>
      <description>&lt;P&gt;i added the buffer of 7 .&lt;/P&gt;</description>
      <pubDate>Thu, 23 Feb 2017 20:01:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/timestamp-parsing-issue-for-a-specific-time/m-p/315183#M94361</guid>
      <dc:creator>kteng2024</dc:creator>
      <dc:date>2017-02-23T20:01:14Z</dc:date>
    </item>
    <item>
      <title>Re: timestamp parsing issue  for a specific time</title>
      <link>https://community.splunk.com/t5/Splunk-Search/timestamp-parsing-issue-for-a-specific-time/m-p/315184#M94362</link>
      <description>&lt;P&gt;Don't do that.&lt;/P&gt;</description>
      <pubDate>Sat, 25 Mar 2017 10:43:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/timestamp-parsing-issue-for-a-specific-time/m-p/315184#M94362</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2017-03-25T10:43:10Z</dc:date>
    </item>
    <item>
      <title>Re: timestamp parsing issue  for a specific time</title>
      <link>https://community.splunk.com/t5/Splunk-Search/timestamp-parsing-issue-for-a-specific-time/m-p/315185#M94363</link>
      <description>&lt;P&gt;You are going to have to find the events that are different that what you are expecting.  Start by searching broadly and using the &lt;CODE&gt;Patterns&lt;/CODE&gt; tab and the &lt;CODE&gt;punct&lt;/CODE&gt; field to discern differences in log structure.&lt;/P&gt;</description>
      <pubDate>Sat, 25 Mar 2017 10:43:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/timestamp-parsing-issue-for-a-specific-time/m-p/315185#M94363</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2017-03-25T10:43:16Z</dc:date>
    </item>
  </channel>
</rss>

