<?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: LINE_BREAKER not working with most basic settings in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/LINE-BREAKER-not-working-with-most-basic-settings/m-p/406964#M72191</link>
    <description>&lt;P&gt;The LINE_BREAKER will not function unless you give it a &lt;CODE&gt;capture group&lt;/CODE&gt; (there is probably an error in your error log if you search for it with something like &lt;CODE&gt;index=_* sourcetype=splunkd LINE_BREAKER capture&lt;/CODE&gt;).  Everything in the &lt;CODE&gt;capture group&lt;/CODE&gt; will be discarded.  The &lt;CODE&gt;capture group&lt;/CODE&gt; may be empty, but it &lt;EM&gt;MUST&lt;/EM&gt; exist.  Try this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;SHOULD_LINEMERGE = false
LINE_BREAKER = {"agent()
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Tue, 29 Sep 2020 22:48:45 GMT</pubDate>
    <dc:creator>woodcock</dc:creator>
    <dc:date>2020-09-29T22:48:45Z</dc:date>
    <item>
      <title>LINE_BREAKER not working with most basic settings</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/LINE-BREAKER-not-working-with-most-basic-settings/m-p/406962#M72189</link>
      <description>&lt;P&gt;I have a json blob, lets ignore the fact it is json for now.  I simply want to force Splunk to break a single blob on a word. &lt;/P&gt;

&lt;P&gt;Where the string {"agent" exists multiple times, these are the the only settings I have set in props for the sourcetype.&lt;/P&gt;

&lt;P&gt;SHOULD_LINEMERGE = false&lt;BR /&gt;
LINE_BREAKER = {"agent&lt;/P&gt;

&lt;P&gt;This should break, but it is not.  Why is Splunk refusing to break this event?  Again, I know this is json, but I want to understand LINE_BREAKER, as I have read about 3 novels on its use, and it repeatedly fails when implemented.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 22:47:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/LINE-BREAKER-not-working-with-most-basic-settings/m-p/406962#M72189</guid>
      <dc:creator>Cuyose</dc:creator>
      <dc:date>2020-09-29T22:47:09Z</dc:date>
    </item>
    <item>
      <title>Re: LINE_BREAKER not working with most basic settings</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/LINE-BREAKER-not-working-with-most-basic-settings/m-p/406963#M72190</link>
      <description>&lt;P&gt;The &lt;CODE&gt;LINE_BREAKER&lt;/CODE&gt; attribute &lt;EM&gt;must&lt;/EM&gt; contain a capture group.  Be warned the contents of the capture group will be discarded so choose it carefully.  It's perfectly legitimate to have an empty capture group as in &lt;CODE&gt;LINE_BREAKER = (){"agent&lt;/CODE&gt;.&lt;/P&gt;</description>
      <pubDate>Wed, 16 Jan 2019 18:17:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/LINE-BREAKER-not-working-with-most-basic-settings/m-p/406963#M72190</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2019-01-16T18:17:48Z</dc:date>
    </item>
    <item>
      <title>Re: LINE_BREAKER not working with most basic settings</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/LINE-BREAKER-not-working-with-most-basic-settings/m-p/406964#M72191</link>
      <description>&lt;P&gt;The LINE_BREAKER will not function unless you give it a &lt;CODE&gt;capture group&lt;/CODE&gt; (there is probably an error in your error log if you search for it with something like &lt;CODE&gt;index=_* sourcetype=splunkd LINE_BREAKER capture&lt;/CODE&gt;).  Everything in the &lt;CODE&gt;capture group&lt;/CODE&gt; will be discarded.  The &lt;CODE&gt;capture group&lt;/CODE&gt; may be empty, but it &lt;EM&gt;MUST&lt;/EM&gt; exist.  Try this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;SHOULD_LINEMERGE = false
LINE_BREAKER = {"agent()
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 29 Sep 2020 22:48:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/LINE-BREAKER-not-working-with-most-basic-settings/m-p/406964#M72191</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2020-09-29T22:48:45Z</dc:date>
    </item>
    <item>
      <title>Re: LINE_BREAKER not working with most basic settings</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/LINE-BREAKER-not-working-with-most-basic-settings/m-p/406965#M72192</link>
      <description>&lt;P&gt;Thanks, I was making it more complicated in my head.  &lt;/P&gt;</description>
      <pubDate>Wed, 16 Jan 2019 18:47:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/LINE-BREAKER-not-working-with-most-basic-settings/m-p/406965#M72192</guid>
      <dc:creator>Cuyose</dc:creator>
      <dc:date>2019-01-16T18:47:24Z</dc:date>
    </item>
    <item>
      <title>Re: LINE_BREAKER not working with most basic settings</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/LINE-BREAKER-not-working-with-most-basic-settings/m-p/406966#M72193</link>
      <description>&lt;P&gt;Missed it by &amp;gt;that&amp;lt; much.&lt;/P&gt;</description>
      <pubDate>Wed, 16 Jan 2019 19:23:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/LINE-BREAKER-not-working-with-most-basic-settings/m-p/406966#M72193</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2019-01-16T19:23:03Z</dc:date>
    </item>
  </channel>
</rss>

