<?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: Multiline event not get breaking properly in middle of indexing in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Multiline-event-not-get-breaking-properly-in-middle-of-indexing/m-p/240858#M188852</link>
    <description>&lt;P&gt;Have you checked splunkd.log for any error messages relating to the LineBreakingProcessor?&lt;/P&gt;

&lt;P&gt;Also, if your events always start with 00000000000, why don't you simplify your props.conf setting to &lt;CODE&gt;BREAK_ONLY_BEFORE=^00000000000&lt;/CODE&gt;?&lt;/P&gt;</description>
    <pubDate>Sat, 20 Aug 2016 00:32:36 GMT</pubDate>
    <dc:creator>s2_splunk</dc:creator>
    <dc:date>2016-08-20T00:32:36Z</dc:date>
    <item>
      <title>Multiline event not get breaking properly in middle of indexing</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Multiline-event-not-get-breaking-properly-in-middle-of-indexing/m-p/240857#M188851</link>
      <description>&lt;P&gt;i am indexing .dat file which contains more than 5000 events.&lt;BR /&gt;
in the middle 1 or 2 events breaked wrongly &lt;BR /&gt;
This the config i used &lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Props.conf&lt;/STRONG&gt; &lt;BR /&gt;
NO_BINARY_CHECK = true&lt;BR /&gt;
BREAK_ONLY_BEFORE = ^\d{1,11}\s?,(([^\,]+)?\,?.?),(([^\,]+)?\,?.?)&lt;BR /&gt;
MAX_TIMESTAMP_LOOKAHEAD = 100&lt;BR /&gt;
TIME_FORMAT = %Y%m%d%H%M%S%6N&lt;BR /&gt;
TIME_PREFIX = ^(?:[^,\n]*,){7}&lt;BR /&gt;
disabled = false&lt;BR /&gt;
pulldown_type = true&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;inputs.conf&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;[monitor:///xxxx]&lt;BR /&gt;
disabled = false&lt;BR /&gt;
whitelist=*.dat&lt;BR /&gt;
time_before_close = 120&lt;BR /&gt;
multiline_event_extra_waittime = true&lt;BR /&gt;
index = xxxx&lt;BR /&gt;
sourcetype = yyyy&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Actual Events&lt;/STRONG&gt; &lt;BR /&gt;
00000000000,,xxxx,40673673,19.08.2016,14:00,21:00,20160818070100184759,/ablive/data/yyyy/serial/yyyy/DISTRIBUTION/DELIVERY/delivery_messages_inbound/pending/./xxxx201608180700060000.csv,xxxx201608180700060000.csv,26,c2038af5-5b95-4532-bfa2-e2fa54d8a29e,22a301ea-26-a666-5e1b87780-ac168f26_57b54f17_2dc00d6-11b7,22a301ea-26-a666-5e1b87780-ac168f26_57b54f17_2dc00d6-1232,2016-08-18T07:01:50.679Z,2016-08-18T07:01:52.994Z,44,GB,Scheduled,Success,SUCCESS,SUCCESS&lt;/P&gt;

&lt;P&gt;00000000000,,xxxx,40667760,19.08.2016,17:00,21:00,20160818070100167747,/ablive/data/yyyy/serial/yyyy/DISTRIBUTION/DELIVERY/delivery_messages_inbound/pending/./xxxx201608180700060000.csv,xxxx201608180700060000.csv,24,854f6e61-bf00-4914-9799-c539eb30be81,22a301ea-26-a666-5e1b87780-ac168f26_57b54f17_2dc00d6-1023,22a301ea-26-a666-5e1b87780-ac168f26_57b54f17_2dc00d6-1066,2016-08-18T07:01:46.089Z,2016-08-18T07:01:49.160Z,44,GB,Scheduled,Success,SUCCESS,SUCCESS&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Indexed Events&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;e,22a301ea-26-a666-5e1b87780-ac168f26_57b54f17_2dc00d6-11b7,22a301ea-26-a666-5e1b87780-ac168f26_57b54f17_2dc00d6-1232,2016-08-18T07:01:50.679Z,2016-08-18T07:01:52.994Z,44,GB,Scheduled,Success,SUCCESS,SUCCESS&lt;/P&gt;

&lt;P&gt;60,19.08.2016,17:00,21:00,20160818070100167747,/ablive/data/yyyy/serial/yyyy/DISTRIBUTION/DELIVERY/delivery_messages_inbound/pending/./xxxx201608180700060000.csv,xxxx201608180700060000.csv,24,854f6e61-bf00-4914-9799-c539eb30be81,22a301ea-26-a666-5e1b87780-ac168f26_57b54f17_2dc00d6-1023,22a301ea-26-a666-5e1b87780-ac168f26_57b54f17_2dc00d6-1066,2016-08-18T07:01:46.089Z,2016-08-18T07:01:49.160Z,44,GB,Scheduled,Success,SUCCESS,SUCCESS&lt;/P&gt;

&lt;P&gt;00000000000,,xxxx,40673673,19.08.2016,14:00,21:00,20160818070100184759,/ablive/data/yyyy/serial/yyyy/DISTRIBUTION/DELIVERY/delivery_messages_inbound/pending/./xxxx201608180700060000.csv,xxxx201608180700060000.csv,26,c2038af5-5b95-4532-bfa2-e2fa54d8a29&lt;/P&gt;

&lt;P&gt;00000000000,,xxxx,406677 &lt;/P&gt;

&lt;P&gt;Indextimings&lt;/P&gt;

&lt;P&gt;indextime                 source    count&lt;BR /&gt;
2016-08-18 07:01:49     xxxx    2162&lt;BR /&gt;
2016-08-18 07:01:52     xxxx         2&lt;BR /&gt;
2016-08-18 07:01:53     xxxx    2137&lt;BR /&gt;
2016-08-18 07:01:56     xxxx    2&lt;BR /&gt;
2016-08-18 07:01:58     xxxx    1266&lt;/P&gt;

&lt;P&gt;same file indexed in above mentioned time and count 2 contains splitted events. &lt;BR /&gt;
I used time_before_close and multiline_event_extra_waittime=true even though 1 or 2 events get splitted.&lt;/P&gt;

&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 10:42:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Multiline-event-not-get-breaking-properly-in-middle-of-indexing/m-p/240857#M188851</guid>
      <dc:creator>arunloganathan</dc:creator>
      <dc:date>2020-09-29T10:42:03Z</dc:date>
    </item>
    <item>
      <title>Re: Multiline event not get breaking properly in middle of indexing</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Multiline-event-not-get-breaking-properly-in-middle-of-indexing/m-p/240858#M188852</link>
      <description>&lt;P&gt;Have you checked splunkd.log for any error messages relating to the LineBreakingProcessor?&lt;/P&gt;

&lt;P&gt;Also, if your events always start with 00000000000, why don't you simplify your props.conf setting to &lt;CODE&gt;BREAK_ONLY_BEFORE=^00000000000&lt;/CODE&gt;?&lt;/P&gt;</description>
      <pubDate>Sat, 20 Aug 2016 00:32:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Multiline-event-not-get-breaking-properly-in-middle-of-indexing/m-p/240858#M188852</guid>
      <dc:creator>s2_splunk</dc:creator>
      <dc:date>2016-08-20T00:32:36Z</dc:date>
    </item>
    <item>
      <title>Re: Multiline event not get breaking properly in middle of indexing</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Multiline-event-not-get-breaking-properly-in-middle-of-indexing/m-p/240859#M188853</link>
      <description>&lt;P&gt;events are not always start with 00000000000. It will have random numbers like 07548521430&lt;/P&gt;</description>
      <pubDate>Mon, 22 Aug 2016 04:58:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Multiline-event-not-get-breaking-properly-in-middle-of-indexing/m-p/240859#M188853</guid>
      <dc:creator>arunloganathan</dc:creator>
      <dc:date>2016-08-22T04:58:20Z</dc:date>
    </item>
    <item>
      <title>Re: Multiline event not get breaking properly in middle of indexing</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Multiline-event-not-get-breaking-properly-in-middle-of-indexing/m-p/240860#M188854</link>
      <description>&lt;P&gt;OK, so what is the pattern then? 1-11 digits, followed by a comma? &lt;BR /&gt;
If so, you could still simplify it by using &lt;CODE&gt;BREAK_ONLY_BEFORE=^\d{1,11},&lt;/CODE&gt;&lt;BR /&gt;
I suspect your line breaking issues stem from an overly complex RegEx, so I would try to use the simplest expression that matches the beginning of your events.&lt;/P&gt;

&lt;P&gt;Did you check splunkd.log for any warning/error messages that may provide a hint as to what may be going on? You may also run into default limits as to total event length and/or maximum number of lines per multi-line event. &lt;/P&gt;</description>
      <pubDate>Mon, 22 Aug 2016 17:58:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Multiline-event-not-get-breaking-properly-in-middle-of-indexing/m-p/240860#M188854</guid>
      <dc:creator>s2_splunk</dc:creator>
      <dc:date>2016-08-22T17:58:06Z</dc:date>
    </item>
    <item>
      <title>Re: Multiline event not get breaking properly in middle of indexing</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Multiline-event-not-get-breaking-properly-in-middle-of-indexing/m-p/240861#M188855</link>
      <description>&lt;P&gt;i checked splunkd.log there is no error or warning events.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Aug 2016 07:55:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Multiline-event-not-get-breaking-properly-in-middle-of-indexing/m-p/240861#M188855</guid>
      <dc:creator>arunloganathan</dc:creator>
      <dc:date>2016-08-23T07:55:54Z</dc:date>
    </item>
    <item>
      <title>Re: Multiline event not get breaking properly in middle of indexing</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Multiline-event-not-get-breaking-properly-in-middle-of-indexing/m-p/240862#M188856</link>
      <description>&lt;P&gt;That actually all looks good. I was going to suggest that possibly an EOF was causing Splunk to split the event. I've had something similar happen before. I think a good test would be taking that log file (the one with 5000 events) uploading it directly to your indexer through the GUI with the "Add Data" feature. Configure everything the same and see if the event is still breaking weird in the middle. I use this method sometimes if it seems like it should be working based on the config. If it works there then it means its something else.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Aug 2016 14:03:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Multiline-event-not-get-breaking-properly-in-middle-of-indexing/m-p/240862#M188856</guid>
      <dc:creator>michael_sleep</dc:creator>
      <dc:date>2016-08-23T14:03:28Z</dc:date>
    </item>
    <item>
      <title>Re: Multiline event not get breaking properly in middle of indexing</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Multiline-event-not-get-breaking-properly-in-middle-of-indexing/m-p/240863#M188857</link>
      <description>&lt;P&gt;I tired indexing data using GUI. There is no issue in line breaking. This line break issue not happened every day . It happens randomly one day 1 event get splitted another day 2 events but not more than 2 events. No issue in some days&lt;/P&gt;</description>
      <pubDate>Wed, 24 Aug 2016 09:40:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Multiline-event-not-get-breaking-properly-in-middle-of-indexing/m-p/240863#M188857</guid>
      <dc:creator>arunloganathan</dc:creator>
      <dc:date>2016-08-24T09:40:36Z</dc:date>
    </item>
  </channel>
</rss>

