<?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 LINE_BREAKER=([\r\n]+) not working? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/LINE-BREAKER-r-n-not-working/m-p/633159#M108411</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have a test instance of splunk - fresh out of the box. Only configure the essentials and imported a dump from the&amp;nbsp; OpenLibrary.org. I have the problem that every single line should be one event but plenty of lines are merged together and I can't figure out why. The source data has reliable linebreaks in so the default should work.&lt;/P&gt;&lt;P&gt;I had the same issue in my enterprise environment and nobody could tell me why this is happening. After a while it magically disappeared and as far as I can tell it has vanished for good but I'd like to understand the reason why this is happening and prevent it from happening again.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Thorsten&lt;/P&gt;</description>
    <pubDate>Fri, 03 Mar 2023 13:19:37 GMT</pubDate>
    <dc:creator>bitnapper</dc:creator>
    <dc:date>2023-03-03T13:19:37Z</dc:date>
    <item>
      <title>LINE_BREAKER=([\r\n]+) not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/LINE-BREAKER-r-n-not-working/m-p/633159#M108411</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have a test instance of splunk - fresh out of the box. Only configure the essentials and imported a dump from the&amp;nbsp; OpenLibrary.org. I have the problem that every single line should be one event but plenty of lines are merged together and I can't figure out why. The source data has reliable linebreaks in so the default should work.&lt;/P&gt;&lt;P&gt;I had the same issue in my enterprise environment and nobody could tell me why this is happening. After a while it magically disappeared and as far as I can tell it has vanished for good but I'd like to understand the reason why this is happening and prevent it from happening again.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Thorsten&lt;/P&gt;</description>
      <pubDate>Fri, 03 Mar 2023 13:19:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/LINE-BREAKER-r-n-not-working/m-p/633159#M108411</guid>
      <dc:creator>bitnapper</dc:creator>
      <dc:date>2023-03-03T13:19:37Z</dc:date>
    </item>
    <item>
      <title>Re: LINE_BREAKER=([\r\n]+) not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/LINE-BREAKER-r-n-not-working/m-p/633238#M108414</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/245847"&gt;@bitnapper&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Without knowing what type of logs you are working with, I would assume your issue might be related to the use of the default &lt;STRONG&gt;LINE_BREAKER&lt;/STRONG&gt; &lt;SPAN&gt;&lt;STRONG&gt;([\r\n]+)&lt;/STRONG&gt;&amp;nbsp;&lt;/SPAN&gt;while also keeping&amp;nbsp;&lt;STRONG&gt;SHOULD_LINEMERGE = true&lt;/STRONG&gt; (default setting).&lt;/P&gt;&lt;P&gt;SHOULD_LINEMERGE explanation from &lt;A href="https://docs.splunk.com/Documentation/Splunk/9.0.4/Admin/Propsconf" target="_self"&gt;props.conf file:&lt;/A&gt;&lt;/P&gt;&lt;PRE&gt;* When you set this to "true", Splunk software combines several lines of data
  into a single multi-line event, based on values you configure
  in the following settings.
* When you set this to "false", Splunk software does not combine lines of
  data into multiline events.&lt;BR /&gt;* Default: true&lt;/PRE&gt;&lt;P&gt;When SHOULD_LINEMERGE is set to true, other settings (BREAK_ONLY_BEFORE_DATE (default),&amp;nbsp;BREAK_ONLY_BEFORE, MUST_BREAK_AFTER...) are used to define how Splunk software builds multi-line events merging previously broken lines.&lt;/P&gt;&lt;P&gt;Also, remember to restart your Splunk instance where the new parsing rules are being applied (tipically HF/INDEXER or all-in-one architecture)&lt;/P&gt;&lt;P&gt;Hope this helps, have a nice day,&lt;/P&gt;&lt;P&gt;Fabrizio&lt;/P&gt;</description>
      <pubDate>Fri, 03 Mar 2023 20:13:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/LINE-BREAKER-r-n-not-working/m-p/633238#M108414</guid>
      <dc:creator>LRF</dc:creator>
      <dc:date>2023-03-03T20:13:28Z</dc:date>
    </item>
    <item>
      <title>Re: LINE_BREAKER=([\r\n]+) not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/LINE-BREAKER-r-n-not-working/m-p/633292#M108422</link>
      <description>&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-right" image-alt="Screenshot 2023-03-04 at 11-17-30 Daten hinzufügen – Sourcetyp festlegen Splunk 9.0.4.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/24190iBFBC492E0BC811B2/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Screenshot 2023-03-04 at 11-17-30 Daten hinzufügen – Sourcetyp festlegen Splunk 9.0.4.png" alt="Screenshot 2023-03-04 at 11-17-30 Daten hinzufügen – Sourcetyp festlegen Splunk 9.0.4.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;Hi Fabrizio,&lt;/P&gt;&lt;P&gt;thanks for you input. I had linemerge to false to avoid exactly that. Also I configure a one-time import via web. I know that splunk likes restarts like a windows 3.11 but there is no point at which one can restart splunk. I goes directly after applying to importing the data.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 04 Mar 2023 10:18:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/LINE-BREAKER-r-n-not-working/m-p/633292#M108422</guid>
      <dc:creator>bitnapper</dc:creator>
      <dc:date>2023-03-04T10:18:33Z</dc:date>
    </item>
  </channel>
</rss>

