<?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: Props.conf and LINE_BREAKER Regex in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Props-conf-and-LINE-BREAKER-Regex/m-p/46559#M11122</link>
    <description>&lt;P&gt;&lt;CODE&gt;LINE_BREAKER&lt;/CODE&gt; gobbles the first capture group.  You might try this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;([\r\n]+)(\d+)(:)(\d+)(:)(\d+)(\.)(\d+)
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Thu, 21 Jul 2011 14:21:03 GMT</pubDate>
    <dc:creator>dwaddle</dc:creator>
    <dc:date>2011-07-21T14:21:03Z</dc:date>
    <item>
      <title>Props.conf and LINE_BREAKER Regex</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Props-conf-and-LINE-BREAKER-Regex/m-p/46558#M11121</link>
      <description>&lt;P&gt;I have created a regex;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;(\d+)(:)(\d+)(:)(\d+)(\.)(\d+)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;To act as my LINE_BREAKER in the props conf file for an app I am currently working on.&lt;BR /&gt;
The log data is generated by a script and the length of each event output by the script is variable in length and contents however the first entry is always a timestamp of the format;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;13:36:18.680336
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;In the documentation is the following paragraph;&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;UL&gt;
&lt;LI&gt;Wherever the regex matches, Splunk considers the start of the first
matching group to be the   end of the
previous event, and considers the end
of the first matching group to be the
start   of the next event.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;From &lt;A href="http://www.splunk.com/base/Documentation/Latest/Admin/Propsconf"&gt;http://www.splunk.com/base/Documentation/Latest/Admin/Propsconf&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Now I understand that as meaning that it will interpret my regex, when a match is made it will move to the end of the matched data and count that as the beginning of my event.&lt;BR /&gt;
Thats not ideal as I really want to keep all the event data, but as a test I tried it and instead it caught all of my event but missed the first two integers of my timestamp like so;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;:36:18.680336
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I assume its my regex or understanding/implementation thats at fault? Any ideas would be appreciated.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jul 2011 12:45:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Props-conf-and-LINE-BREAKER-Regex/m-p/46558#M11121</guid>
      <dc:creator>Drainy</dc:creator>
      <dc:date>2011-07-21T12:45:27Z</dc:date>
    </item>
    <item>
      <title>Re: Props.conf and LINE_BREAKER Regex</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Props-conf-and-LINE-BREAKER-Regex/m-p/46559#M11122</link>
      <description>&lt;P&gt;&lt;CODE&gt;LINE_BREAKER&lt;/CODE&gt; gobbles the first capture group.  You might try this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;([\r\n]+)(\d+)(:)(\d+)(:)(\d+)(\.)(\d+)
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 21 Jul 2011 14:21:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Props-conf-and-LINE-BREAKER-Regex/m-p/46559#M11122</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2011-07-21T14:21:03Z</dc:date>
    </item>
  </channel>
</rss>

