<?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 Custom multi-line parsing tip in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Custom-multi-line-parsing-tip/m-p/12763#M1075</link>
    <description>&lt;P&gt;I want to chop multiline events like below.  I had splunk to automatically process the data, but it didn't quite work where the event started with "Begin_Event".&lt;BR /&gt;
How can I define custom event separation rule so that the each evens starts after "Begin_Event" tag?  &lt;/P&gt;

&lt;P&gt;(Begin_Event)&lt;/P&gt;

&lt;P&gt;environmentFailureEvent  -  EAS  -  KG-079, Cab 1, Pos 1,  active ACG, EAS 0  -  May  3, 2010  00:02:55.
  [247]  Rectifier Module Fail                               -  Clear&lt;BR /&gt;
(EndEvent)&lt;/P&gt;

&lt;P&gt;(BeginEvent)&lt;/P&gt;

&lt;P&gt;processingFailureEvent  -  IHLR_ALARM_APP  -  KTIHLR1_B, IHLR_ALARM_APP 1  -  May  3, 2010  00:02:49.
  [17260]  Subscriber Not In iDEN HLR  -  Minor.
  RC:77 imsi=450079680700513&lt;/P&gt;

&lt;P&gt;(EndEvent)&lt;/P&gt;</description>
    <pubDate>Mon, 03 May 2010 16:40:38 GMT</pubDate>
    <dc:creator>clyde772</dc:creator>
    <dc:date>2010-05-03T16:40:38Z</dc:date>
    <item>
      <title>Custom multi-line parsing tip</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Custom-multi-line-parsing-tip/m-p/12763#M1075</link>
      <description>&lt;P&gt;I want to chop multiline events like below.  I had splunk to automatically process the data, but it didn't quite work where the event started with "Begin_Event".&lt;BR /&gt;
How can I define custom event separation rule so that the each evens starts after "Begin_Event" tag?  &lt;/P&gt;

&lt;P&gt;(Begin_Event)&lt;/P&gt;

&lt;P&gt;environmentFailureEvent  -  EAS  -  KG-079, Cab 1, Pos 1,  active ACG, EAS 0  -  May  3, 2010  00:02:55.
  [247]  Rectifier Module Fail                               -  Clear&lt;BR /&gt;
(EndEvent)&lt;/P&gt;

&lt;P&gt;(BeginEvent)&lt;/P&gt;

&lt;P&gt;processingFailureEvent  -  IHLR_ALARM_APP  -  KTIHLR1_B, IHLR_ALARM_APP 1  -  May  3, 2010  00:02:49.
  [17260]  Subscriber Not In iDEN HLR  -  Minor.
  RC:77 imsi=450079680700513&lt;/P&gt;

&lt;P&gt;(EndEvent)&lt;/P&gt;</description>
      <pubDate>Mon, 03 May 2010 16:40:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Custom-multi-line-parsing-tip/m-p/12763#M1075</guid>
      <dc:creator>clyde772</dc:creator>
      <dc:date>2010-05-03T16:40:38Z</dc:date>
    </item>
    <item>
      <title>Re: Custom multi-line parsing tip</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Custom-multi-line-parsing-tip/m-p/12764#M1076</link>
      <description>&lt;P&gt;Just set:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;SHOULD_LINEMERGE = false
BREAK_ONLY_BEFORE = ^\(Begin_Event\)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;for your sourcetype or source in props.conf. Alternatively you could use:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;SHOULD_LINEMERGE = false
LINE_BREAKER = ([\r\n]+)(?=\(Begin_Event\))
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Variations of the above can remove the &lt;CODE&gt;(Begin_Event)&lt;/CODE&gt; line as well.&lt;/P&gt;</description>
      <pubDate>Tue, 04 May 2010 01:02:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Custom-multi-line-parsing-tip/m-p/12764#M1076</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2010-05-04T01:02:03Z</dc:date>
    </item>
  </channel>
</rss>

