<?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: striptime not parsing time stamps in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/striptime-not-parsing-time-stamps/m-p/54659#M10615</link>
    <description>&lt;P&gt;Work great thanks!&lt;/P&gt;</description>
    <pubDate>Thu, 05 Sep 2013 09:51:10 GMT</pubDate>
    <dc:creator>smudge797</dc:creator>
    <dc:date>2013-09-05T09:51:10Z</dc:date>
    <item>
      <title>striptime not parsing time stamps</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/striptime-not-parsing-time-stamps/m-p/54655#M10611</link>
      <description>&lt;P&gt;Im having trouble with data previewer not recognizing the striptime in my logs.  Any help would be much welcome!  Thanks in advance.&lt;/P&gt;

&lt;P&gt;In my props.conf have tried:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[test_data]
TIME_FORMAT=%d %b %Y %H:%M:%S,%3N
TIME_PREFIX =) 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Sample data:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;FATAL http-bio-7779-exec-12 com.mydomain.bux.common.client.HttpServiceInvoker (HttpServiceResult.java:90) 30 Aug 2013 00:24:16,407 - Http Service Calling Failed. Http Calling Context: 

FATAL http-bio-7779-exec-12 com.mydomain.bux.common.client.HttpServiceInvoker (HttpServiceResult.java:90) 30 Aug 2013 00:24:16,431 - Http Service Calling Failed. Http Calling Context: 

FATAL http-bio-7779-exec-12 com.mydomain.bux.common.client.HttpServiceInvoker (HttpServiceResult.java:90) 30 Aug 2013 00:24:16,437 - Http Service Calling Failed. Http Calling Context: 

ERROR http-bio-7779-exec-12 com.mydomain.bux.webservice.callstoactionsvc.serviceclients.MyServiceClientImpl (LoggingUtils.java:56) 30 Aug 2013 00:24:16,475 - CallsToActionSvcException occurs when trying to process the reqeust.

ERROR http-bio-7779-exec-12 com.mydomain.bux.webservice.callstoactionsvc.serviceclients.YourServiceClientImpl (LoggingUtils.java:56) 30 Aug 2013 00:24:16,525 - CallsToActionSvcException occurs when trying to process the reqeust.

ERROR http-bio-7779-exec-12 com.mydomain.bux.webservice.callstoactionsvc.serviceclients.MyServiceClientImpl (LoggingUtils.java:56) 30 Aug 2013 00:24:16,569 - CallsToActionSvcException occurs when trying to process the reqeust.

FATAL http-bio-7779-exec-12 com.mydomain.bux.common.client.HttpServiceInvoker (HttpServiceResult.java:90) 30 Aug 2013 00:24:30,316 - Http Service Calling Failed. Http Calling Context: 

FATAL http-bio-7779-exec-12 com.mydomain.bux.common.client.HttpServiceInvoker (HttpServiceResult.java:90) 30 Aug 2013 00:24:30,323 - Http Service Calling Failed. Http Calling Context: 
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 04 Sep 2013 14:02:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/striptime-not-parsing-time-stamps/m-p/54655#M10611</guid>
      <dc:creator>smudge797</dc:creator>
      <dc:date>2013-09-04T14:02:08Z</dc:date>
    </item>
    <item>
      <title>Re: striptime not parsing time stamps</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/striptime-not-parsing-time-stamps/m-p/54656#M10612</link>
      <description>&lt;P&gt;Hi Smudge,&lt;/P&gt;

&lt;P&gt;Try this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[test_data]
MAX_TIMESTAMP_LOOKAHEAD = 200
NO_BINARY_CHECK = 1
SHOULD_LINEMERGE = false
TIME_FORMAT = %d %b %Y %H:%M:%S,%3N
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I think your problem is that on some lines the timestamp is more than 150 characters into the event (which by default is where Splunk will search to.&lt;/P&gt;

&lt;P&gt;Let me know how you get along &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Ref:&lt;/STRONG&gt; &lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.4/Data/Configuretimestamprecognition#Timestamp_attributes"&gt;http://docs.splunk.com/Documentation/Splunk/5.0.4/Data/Configuretimestamprecognition#Timestamp_attributes&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Sep 2013 14:40:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/striptime-not-parsing-time-stamps/m-p/54656#M10612</guid>
      <dc:creator>rturk</dc:creator>
      <dc:date>2013-09-04T14:40:22Z</dc:date>
    </item>
    <item>
      <title>Re: striptime not parsing time stamps</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/striptime-not-parsing-time-stamps/m-p/54657#M10613</link>
      <description>&lt;P&gt;The  &lt;CODE&gt;TIME_FORMAT&lt;/CODE&gt; looks OK, and these are all just single line events, right? And the timestamp will always come within the first 150 characters of the event, right?&lt;/P&gt;

&lt;P&gt;The only thing left to test should be to escape the closing parenthesis in your &lt;CODE&gt;TIME_PREFIX&lt;/CODE&gt;, as parentheses have special meaning in regex, and also add that whitespace for good measure;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;TIME_PREFIX = \)\s
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;And you are aware that this change will only affect new events coming in for indexing. You might have to restart splunk, since this affects index-time operations.&lt;/P&gt;

&lt;P&gt;Hope this helps,&lt;/P&gt;

&lt;P&gt;K&lt;/P&gt;</description>
      <pubDate>Wed, 04 Sep 2013 14:42:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/striptime-not-parsing-time-stamps/m-p/54657#M10613</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2013-09-04T14:42:34Z</dc:date>
    </item>
    <item>
      <title>Re: striptime not parsing time stamps</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/striptime-not-parsing-time-stamps/m-p/54658#M10614</link>
      <description>&lt;P&gt;Good point on the SHOULD_LINEMERGE part. Didn't look like it was past the 150-mark to me, though.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Sep 2013 14:47:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/striptime-not-parsing-time-stamps/m-p/54658#M10614</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2013-09-04T14:47:35Z</dc:date>
    </item>
    <item>
      <title>Re: striptime not parsing time stamps</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/striptime-not-parsing-time-stamps/m-p/54659#M10615</link>
      <description>&lt;P&gt;Work great thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 05 Sep 2013 09:51:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/striptime-not-parsing-time-stamps/m-p/54659#M10615</guid>
      <dc:creator>smudge797</dc:creator>
      <dc:date>2013-09-05T09:51:10Z</dc:date>
    </item>
    <item>
      <title>Re: striptime not parsing time stamps</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/striptime-not-parsing-time-stamps/m-p/54660#M10616</link>
      <description>&lt;P&gt;Please mark it as answered if your problem was solved. Vote up if you want to. &lt;/P&gt;

&lt;P&gt;Thanks,&lt;BR /&gt;
K&lt;/P&gt;</description>
      <pubDate>Thu, 05 Sep 2013 16:25:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/striptime-not-parsing-time-stamps/m-p/54660#M10616</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2013-09-05T16:25:01Z</dc:date>
    </item>
    <item>
      <title>Re: striptime not parsing time stamps</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/striptime-not-parsing-time-stamps/m-p/54661#M10617</link>
      <description>&lt;P&gt;Worked great thanks!&lt;/P&gt;</description>
      <pubDate>Sat, 22 Mar 2014 20:56:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/striptime-not-parsing-time-stamps/m-p/54661#M10617</guid>
      <dc:creator>smudge797</dc:creator>
      <dc:date>2014-03-22T20:56:21Z</dc:date>
    </item>
  </channel>
</rss>

