<?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: Why is BREAK_ONLY_BEFORE not working as expected for all my events? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-BREAK-ONLY-BEFORE-not-working-as-expected-for-all-my/m-p/233948#M45581</link>
    <description>&lt;P&gt;Can you let us know exactly what your props.conf looks like for this sourcetype now? &lt;/P&gt;</description>
    <pubDate>Mon, 11 Jul 2016 14:13:16 GMT</pubDate>
    <dc:creator>ryanoconnor</dc:creator>
    <dc:date>2016-07-11T14:13:16Z</dc:date>
    <item>
      <title>Why is BREAK_ONLY_BEFORE not working as expected for all my events?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-BREAK-ONLY-BEFORE-not-working-as-expected-for-all-my/m-p/233942#M45575</link>
      <description>&lt;P&gt;I am using the following configuration in props.conf. It is splitting most of the events correctly, but 2 or 3 events are collapsed.  Should I need to include &lt;CODE&gt;SHOULD_LINEMERGE = false&lt;/CODE&gt;?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[my_source_type]
NO_BINARY_CHECK = true
BREAK_ONLY_BEFORE = ^\d{1,11}\s?,(([^\,]+)?\,?\.?),(([^\,]+)?\,?\.?)
MAX_TIMESTAMP_LOOKAHEAD = 100
TIME_FORMAT = %Y%m%d%H%M%S%6N
TIME_PREFIX = ^(?:[^,\n]*,){7}
disabled = false
pulldown_type = true
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This is a .dat file and it has more than 8000 events on a single file. &lt;/P&gt;

&lt;P&gt;Sample data&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Actual events&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;07986376244,Mrs,xxxx,40369036,29.06.2016,14:00,21:00,20160628070106529271,/ablive/data/xx/serial/yy/DISTRIBUTION/DELIVERY/delivery_messages_inbound/pending/./MessageReminderPM201606280700120000.csv,MessageReminderPM201606280700120000.csv,38,4c7ca670-eddf-4362-8f4b-20ea99007a0b,225b00fe-26-a633-5e21f14e2-ac168f26_5772129e_37501fc-1b5a,225b00fe-26-a633-5e21f14e2-ac168f26_5772129e_37501fc-1bca,2016-06-28T07:02:23.224Z,2016-06-28T07:02:26.890Z,44,GB,Scheduled,Success,SUCCESS,SUCCESS

07941158158,Mr,yyyyy,40360516,29.06.2016,14:00,21:00,20160628070106516893,/ablive/data/xx/serial/yy/DISTRIBUTION/DELIVERY/delivery_messages_inbound/pending/./MessageReminderPM201606280700120000.csv,MessageReminderPM201606280700120000.csv,36,4a140e0f-69e4-44d3-a5ce-dfb186c9a081,225b00fe-26-a633-5e21f14e2-ac168f26_5772129e_37501fc-19c6,225b00fe-26-a633-5e21f14e2-ac168f26_5772129e_37501fc-1a2f,2016-06-28T07:02:17.050Z,2016-06-28T07:02:19.816Z,44,GB,Scheduled,Success,SUCCESS,SUCCESS
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;STRONG&gt;indexed events&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;ELIVERY/delivery_messages_inbound/pending/./MessageReminderPM201606280700120000.csv,MessageReminderPM201606280700120000.csv,38,4c7ca670-eddf-4362-8f4b-20ea99007a0b,225b00fe-26-a633-5e21f14e2-ac168f26_5772129e_37501fc-1b5a,225b00fe-26-a633-5e21f14e2-ac168f26_5772129e_37501fc-1bca,2016-06-28T07:02:23.224Z,2016-06-28T07:02:26.890Z,44,GB,Scheduled,Success,SUCCESS,SUCCESS
xx/serial/JL/DISTRIBUTION/DELIVERY/delivery_messages_inbound/pending/./MessageReminderPM201606280700120000.csv,MessageReminderPM201606280700120000.csv,36,4a140e0f-69e4-44d3-a5ce-dfb186c9a081,225b00fe-26-a633-5e21f14e2-ac168f26_5772129e_37501fc-19c6,225b00fe-26-a633-5e21f14e2-ac168f26_5772129e_37501fc-1a2f,2016-06-28T07:02:17.050Z,2016-06-28T07:02:19.816Z,44,GB,Scheduled,Success,SUCCESS,SUCCESS
07986356244,Mrs,Mason,40369036,29.06.2016,14:00,21:00,20160628070106529271,/ablive/data/xx/serial/yy/DISTRIBUTION/D
07941156158,Mr,Hurley,40360516,29.06.2016,14:00,21:00,20160628070106516893,/ablive/data/
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Thanks in advance &lt;/P&gt;</description>
      <pubDate>Wed, 29 Jun 2016 07:22:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-BREAK-ONLY-BEFORE-not-working-as-expected-for-all-my/m-p/233942#M45575</guid>
      <dc:creator>arunloganathan</dc:creator>
      <dc:date>2016-06-29T07:22:26Z</dc:date>
    </item>
    <item>
      <title>Re: Why is BREAK_ONLY_BEFORE not working as expected for all my events?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-BREAK-ONLY-BEFORE-not-working-as-expected-for-all-my/m-p/233943#M45576</link>
      <description>&lt;P&gt;This appears to be a csv file. Have you tried indexed_extractions? &lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.4.1/Data/Extractfieldsfromfileswithstructureddata"&gt;http://docs.splunk.com/Documentation/Splunk/6.4.1/Data/Extractfieldsfromfileswithstructureddata&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 08 Jul 2016 17:22:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-BREAK-ONLY-BEFORE-not-working-as-expected-for-all-my/m-p/233943#M45576</guid>
      <dc:creator>sundareshr</dc:creator>
      <dc:date>2016-07-08T17:22:44Z</dc:date>
    </item>
    <item>
      <title>Re: Why is BREAK_ONLY_BEFORE not working as expected for all my events?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-BREAK-ONLY-BEFORE-not-working-as-expected-for-all-my/m-p/233944#M45577</link>
      <description>&lt;P&gt;You should specify SHOULD_LINEMERGE = true if you want to use BREAK_ONLY_BEFORE, etc.  It's not required though.&lt;/P&gt;

&lt;P&gt;Sorry for so many versions of this answer... i get confused on this one all the time &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;Here's the section in props.conf:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.4.1/Admin/Propsconf#Line_breaking" target="_blank"&gt;http://docs.splunk.com/Documentation/Splunk/6.4.1/Admin/Propsconf#Line_breaking&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;See if this works:&lt;/P&gt;

&lt;P&gt;BREAK_ONLY_BEFORE = \d{1,11}\s?,(([^\,]+)?\,?.?),(([^\,]+)?\,?.?)&lt;/P&gt;

&lt;P&gt;Note about BREAK_ONLY_BEFORE&lt;BR /&gt;
* When set, Splunk creates a new event &lt;STRONG&gt;&lt;EM&gt;only if it encounters a new line that&lt;BR /&gt;
  matches the regular expression&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;I like the idea of using INDEXED_EXTRACTIONS = CSV instead.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 10:10:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-BREAK-ONLY-BEFORE-not-working-as-expected-for-all-my/m-p/233944#M45577</guid>
      <dc:creator>jkat54</dc:creator>
      <dc:date>2020-09-29T10:10:50Z</dc:date>
    </item>
    <item>
      <title>Re: Why is BREAK_ONLY_BEFORE not working as expected for all my events?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-BREAK-ONLY-BEFORE-not-working-as-expected-for-all-my/m-p/233945#M45578</link>
      <description>&lt;P&gt;Just to note, it's recommended to &lt;STRONG&gt;not&lt;/STRONG&gt; use SHOULD_LINEMERGE = true if you can help it. You'll notice significant performance gains by not using that setting as it rules out an entire portion of the data pipeline. &lt;/P&gt;</description>
      <pubDate>Fri, 08 Jul 2016 18:42:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-BREAK-ONLY-BEFORE-not-working-as-expected-for-all-my/m-p/233945#M45578</guid>
      <dc:creator>ryanoconnor</dc:creator>
      <dc:date>2016-07-08T18:42:25Z</dc:date>
    </item>
    <item>
      <title>Re: Why is BREAK_ONLY_BEFORE not working as expected for all my events?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-BREAK-ONLY-BEFORE-not-working-as-expected-for-all-my/m-p/233946#M45579</link>
      <description>&lt;P&gt;Give this a try&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; [my_source_type]
 NO_BINARY_CHECK = true
 LINE_BREAKER= ([\r\n]+)(\d{1,11}\s?,(([^\,]+)?\,?\.?),(([^\,]+)?\,?\.?))
 MAX_TIMESTAMP_LOOKAHEAD = 20
 TIME_FORMAT = %Y%m%d%H%M%S%6N
 TIME_PREFIX = ^(?:[^,\n]*,){7}
 SHOULD_LINEMERGE = false
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 08 Jul 2016 21:39:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-BREAK-ONLY-BEFORE-not-working-as-expected-for-all-my/m-p/233946#M45579</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2016-07-08T21:39:20Z</dc:date>
    </item>
    <item>
      <title>Re: Why is BREAK_ONLY_BEFORE not working as expected for all my events?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-BREAK-ONLY-BEFORE-not-working-as-expected-for-all-my/m-p/233947#M45580</link>
      <description>&lt;P&gt;i tired indexed_extractions as csv. All events get merged as 1 single event&lt;/P&gt;</description>
      <pubDate>Mon, 11 Jul 2016 09:52:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-BREAK-ONLY-BEFORE-not-working-as-expected-for-all-my/m-p/233947#M45580</guid>
      <dc:creator>arunloganathan</dc:creator>
      <dc:date>2016-07-11T09:52:30Z</dc:date>
    </item>
    <item>
      <title>Re: Why is BREAK_ONLY_BEFORE not working as expected for all my events?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-BREAK-ONLY-BEFORE-not-working-as-expected-for-all-my/m-p/233948#M45581</link>
      <description>&lt;P&gt;Can you let us know exactly what your props.conf looks like for this sourcetype now? &lt;/P&gt;</description>
      <pubDate>Mon, 11 Jul 2016 14:13:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-BREAK-ONLY-BEFORE-not-working-as-expected-for-all-my/m-p/233948#M45581</guid>
      <dc:creator>ryanoconnor</dc:creator>
      <dc:date>2016-07-11T14:13:16Z</dc:date>
    </item>
  </channel>
</rss>

