<?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: Cannot merge events MUST NOT BREAK BEFORE not sticking. in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Cannot-merge-events-MUST-NOT-BREAK-BEFORE-not-sticking/m-p/252438#M48524</link>
    <description>&lt;P&gt;Hi twinspop thanks so much for your suggestion.  Unfortunately there is no change:&lt;/P&gt;

&lt;P&gt;My new indexer props.conf (and subsequent indexer restart after):&lt;/P&gt;

&lt;P&gt;[wrkflowsched_log]&lt;BR /&gt;
SHOULD_LINEMEREGE = false&lt;BR /&gt;
LINE_BREAKER = (To finish press any key.)    &lt;/P&gt;

&lt;P&gt;(i had removed the quotation in your regex as it is not part of the text)&lt;/P&gt;

&lt;P&gt;I then created a new log file adding a line, saved it.  It appears as an event.  I added another line and saved it.  It appears as a second event.  Same issue.&lt;/P&gt;

&lt;P&gt;Interestingly enough, I also created a larger log file with this text:&lt;/P&gt;

&lt;P&gt;TEST line 1&lt;BR /&gt;
TEST line 2&lt;BR /&gt;
TEST line 3&lt;BR /&gt;
TEST line 4&lt;BR /&gt;
TEST line 5&lt;BR /&gt;
To finish press any key.&lt;BR /&gt;
Test line 6&lt;/P&gt;

&lt;P&gt;This is how the singular event is shown in the Splunk indexer with your props stanza:&lt;/P&gt;

&lt;P&gt;TEST line 1&lt;BR /&gt;
TEST line 2&lt;BR /&gt;
TEST line 3&lt;BR /&gt;
TEST line 4&lt;BR /&gt;
TEST line 5&lt;/P&gt;

&lt;P&gt;Test line 6&lt;/P&gt;

&lt;P&gt;So it just removed the line.  This isn't my goal BUT it gives me hope that the props.conf is actually being read.  I also attempted adding your regex to the MNBB statement (thinking the initial problem was my regex) but it changed nothing.  Same problem.  1 line = 1 event.&lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 10:46:22 GMT</pubDate>
    <dc:creator>alexsambacanada</dc:creator>
    <dc:date>2020-09-29T10:46:22Z</dc:date>
    <item>
      <title>Cannot merge events MUST NOT BREAK BEFORE not sticking.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Cannot-merge-events-MUST-NOT-BREAK-BEFORE-not-sticking/m-p/252436#M48522</link>
      <description>&lt;P&gt;Hello!  &lt;/P&gt;

&lt;P&gt;Our application creates a log file a day.  In the log file, every line is divided into a separate event.  I am trying to have Splunk merge all the lines into one event.  Simple right?  Not in my case apparently.  &lt;/P&gt;

&lt;P&gt;At the end of the log is this text: &lt;STRONG&gt;Batch tasks have been completed. To finish press any key.&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;Example:&lt;/P&gt;

&lt;P&gt;"Upload of C:\OESP_DATA\Feeds\Daily\MOF\request\ESPIncReq_P_3119_20160826_T014444.xml.ent succeeded&lt;BR /&gt;
Finished building request for MOF.........&lt;BR /&gt;
Finished putting files........&lt;BR /&gt;
&lt;STRONG&gt;Batch tasks have been completed. To finish press any key."&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;So I have added this stanza to my props.conf on the indexer:&lt;/P&gt;

&lt;P&gt;[wrkflowsched_log]&lt;BR /&gt;
SHOULD_LINEMERGE = True&lt;BR /&gt;
MUST_NOT_BREAK_BEFORE = Batch tasks have been completed&lt;/P&gt;

&lt;P&gt;I have also tried this regex for the MUST_NOT_BREAK_BEFORE statement:&lt;BR /&gt;
MUST_NOT_BREAK_BEFORE =  /Batch tasks have been completed. To finish press any key/&lt;BR /&gt;
(Which seems to match up at regexr.com)&lt;/P&gt;

&lt;P&gt;wrkflowsched_log is the sourcetype&lt;/P&gt;

&lt;P&gt;I then proceed to restart the indexer and write a new file in the targeted log directory on the source.  I write some text, save it and then write another line and save it.  Repeatedly every line shows as a new event even though I have not written the &lt;STRONG&gt;Batch tasks have been completed&lt;/STRONG&gt; statement.&lt;/P&gt;

&lt;P&gt;I have verified there is no props.conf in the local folder on the source.  &lt;/P&gt;

&lt;P&gt;Any thoughts?&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;

&lt;P&gt;AlexW&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 10:46:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Cannot-merge-events-MUST-NOT-BREAK-BEFORE-not-sticking/m-p/252436#M48522</guid>
      <dc:creator>alexsambacanada</dc:creator>
      <dc:date>2020-09-29T10:46:19Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot merge events MUST NOT BREAK BEFORE not sticking.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Cannot-merge-events-MUST-NOT-BREAK-BEFORE-not-sticking/m-p/252437#M48523</link>
      <description>&lt;P&gt;I'm not sure MNBB is what you want. I'd use LINE_BREAKER instead anyway:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;SHOULD_LINEMEREGE = false
LINE_BREAKER = (To finish press any key.")
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Note the part of the regex in parens will be consumed and NOT indexed. Adjust as appropriate. &lt;/P&gt;</description>
      <pubDate>Sat, 27 Aug 2016 23:06:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Cannot-merge-events-MUST-NOT-BREAK-BEFORE-not-sticking/m-p/252437#M48523</guid>
      <dc:creator>twinspop</dc:creator>
      <dc:date>2016-08-27T23:06:45Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot merge events MUST NOT BREAK BEFORE not sticking.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Cannot-merge-events-MUST-NOT-BREAK-BEFORE-not-sticking/m-p/252438#M48524</link>
      <description>&lt;P&gt;Hi twinspop thanks so much for your suggestion.  Unfortunately there is no change:&lt;/P&gt;

&lt;P&gt;My new indexer props.conf (and subsequent indexer restart after):&lt;/P&gt;

&lt;P&gt;[wrkflowsched_log]&lt;BR /&gt;
SHOULD_LINEMEREGE = false&lt;BR /&gt;
LINE_BREAKER = (To finish press any key.)    &lt;/P&gt;

&lt;P&gt;(i had removed the quotation in your regex as it is not part of the text)&lt;/P&gt;

&lt;P&gt;I then created a new log file adding a line, saved it.  It appears as an event.  I added another line and saved it.  It appears as a second event.  Same issue.&lt;/P&gt;

&lt;P&gt;Interestingly enough, I also created a larger log file with this text:&lt;/P&gt;

&lt;P&gt;TEST line 1&lt;BR /&gt;
TEST line 2&lt;BR /&gt;
TEST line 3&lt;BR /&gt;
TEST line 4&lt;BR /&gt;
TEST line 5&lt;BR /&gt;
To finish press any key.&lt;BR /&gt;
Test line 6&lt;/P&gt;

&lt;P&gt;This is how the singular event is shown in the Splunk indexer with your props stanza:&lt;/P&gt;

&lt;P&gt;TEST line 1&lt;BR /&gt;
TEST line 2&lt;BR /&gt;
TEST line 3&lt;BR /&gt;
TEST line 4&lt;BR /&gt;
TEST line 5&lt;/P&gt;

&lt;P&gt;Test line 6&lt;/P&gt;

&lt;P&gt;So it just removed the line.  This isn't my goal BUT it gives me hope that the props.conf is actually being read.  I also attempted adding your regex to the MNBB statement (thinking the initial problem was my regex) but it changed nothing.  Same problem.  1 line = 1 event.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 10:46:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Cannot-merge-events-MUST-NOT-BREAK-BEFORE-not-sticking/m-p/252438#M48524</guid>
      <dc:creator>alexsambacanada</dc:creator>
      <dc:date>2020-09-29T10:46:22Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot merge events MUST NOT BREAK BEFORE not sticking.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Cannot-merge-events-MUST-NOT-BREAK-BEFORE-not-sticking/m-p/252439#M48525</link>
      <description>&lt;P&gt;Interesting. Is the file written a line at a time like that, or all at once in a batch-like fashion? If a line at a time, I might change to break on new line by default, then use transaction to put them back together into one event: &lt;CODE&gt;... | transaction maxevents=5000 source&lt;/CODE&gt; Adjust maxevents as required. &lt;/P&gt;</description>
      <pubDate>Sun, 28 Aug 2016 19:34:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Cannot-merge-events-MUST-NOT-BREAK-BEFORE-not-sticking/m-p/252439#M48525</guid>
      <dc:creator>twinspop</dc:creator>
      <dc:date>2016-08-28T19:34:13Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot merge events MUST NOT BREAK BEFORE not sticking.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Cannot-merge-events-MUST-NOT-BREAK-BEFORE-not-sticking/m-p/252440#M48526</link>
      <description>&lt;P&gt;Hey Twinspop, this was it.  I abondoned the initial approve and grouped the events together with the transaction command using startswith and endswith.  Working great so far.  Thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 08 Sep 2016 19:43:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Cannot-merge-events-MUST-NOT-BREAK-BEFORE-not-sticking/m-p/252440#M48526</guid>
      <dc:creator>alexsambacanada</dc:creator>
      <dc:date>2016-09-08T19:43:31Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot merge events MUST NOT BREAK BEFORE not sticking.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Cannot-merge-events-MUST-NOT-BREAK-BEFORE-not-sticking/m-p/252441#M48527</link>
      <description>&lt;P&gt;Awesome. Glad I could help!&lt;/P&gt;</description>
      <pubDate>Thu, 08 Sep 2016 20:38:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Cannot-merge-events-MUST-NOT-BREAK-BEFORE-not-sticking/m-p/252441#M48527</guid>
      <dc:creator>twinspop</dc:creator>
      <dc:date>2016-09-08T20:38:26Z</dc:date>
    </item>
  </channel>
</rss>

