<?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: Opsec_lea not breaking even reliably in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Opsec-lea-not-breaking-even-reliably/m-p/58186#M11402</link>
    <description>&lt;P&gt;It's probably just because of the default &lt;CODE&gt;MAX_EVENTS&lt;/CODE&gt; setting of 256. Just add:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;MAX_EVENTS=999999
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;to your props.conf rules for the sourcetype.&lt;/P&gt;</description>
    <pubDate>Sun, 13 Mar 2011 01:11:53 GMT</pubDate>
    <dc:creator>gkanapathy</dc:creator>
    <dc:date>2011-03-13T01:11:53Z</dc:date>
    <item>
      <title>Opsec_lea not breaking even reliably</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Opsec-lea-not-breaking-even-reliably/m-p/58185#M11401</link>
      <description>&lt;P&gt;i have the lea-loggrabber.sh script working well and reliably getting all new logs from checkpoint cma into splunk.  I am starting to notice that about 10 messages per 24 hours are not breaking correctly.  They end up being around 257 lines long before the event breaks.  &lt;/P&gt;

&lt;P&gt;how can i force the events to be broken reliably when imported by the lea-loggrabber.sh?&lt;/P&gt;

&lt;P&gt;all events start with loc= and should end with \r\n&lt;/P&gt;

&lt;P&gt;I have the sourcetype set in inputs.conf where the script is called&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[script:///opt/splunkbeta/etc/apps/lea-loggrabber-splunk/bin/lea-loggrabber.sh]
disabled = 0
sourcetype = checkpoint_firewall
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I am attempting to set the linebreaking in the props.conf&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[checkpoint_firewall]
TIME_PREFIX= time=
TIME_FORMAT= %d%b%Y %H:%M:%S
BREAK_ONLY_BEFORE=loc
#LINE_BREAKER = ([\r\n]+)(?=loc\=)
#LINE_BREAKER = ([\r\n])(?=loc\=)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;You can see my attempts at forcing a new event in the comments above.&lt;/P&gt;

&lt;P&gt;Any suggestions on how to force a linebreak for these events?&lt;/P&gt;</description>
      <pubDate>Sun, 13 Mar 2011 00:57:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Opsec-lea-not-breaking-even-reliably/m-p/58185#M11401</guid>
      <dc:creator>EricPartington</dc:creator>
      <dc:date>2011-03-13T00:57:14Z</dc:date>
    </item>
    <item>
      <title>Re: Opsec_lea not breaking even reliably</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Opsec-lea-not-breaking-even-reliably/m-p/58186#M11402</link>
      <description>&lt;P&gt;It's probably just because of the default &lt;CODE&gt;MAX_EVENTS&lt;/CODE&gt; setting of 256. Just add:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;MAX_EVENTS=999999
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;to your props.conf rules for the sourcetype.&lt;/P&gt;</description>
      <pubDate>Sun, 13 Mar 2011 01:11:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Opsec-lea-not-breaking-even-reliably/m-p/58186#M11402</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2011-03-13T01:11:53Z</dc:date>
    </item>
    <item>
      <title>Re: Opsec_lea not breaking even reliably</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Opsec-lea-not-breaking-even-reliably/m-p/58187#M11403</link>
      <description>&lt;P&gt;If that gives me events that could have 9999999 lines in them, then i would want the opposite (MAX_EVENTS=1).  I think i solved it with the ALWAYS_BREAK_BEFORE=loc (had to restart the splunk daemon).&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 09:26:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Opsec-lea-not-breaking-even-reliably/m-p/58187#M11403</guid>
      <dc:creator>EricPartington</dc:creator>
      <dc:date>2020-09-28T09:26:09Z</dc:date>
    </item>
  </channel>
</rss>

