<?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: Multiple lines are getting stuck together at indexing in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Multiple-lines-are-getting-stuck-together-at-indexing/m-p/86999#M18065</link>
    <description>&lt;P&gt;took me a while to get this implemented, but I just did and it worked. thanks so much!&lt;/P&gt;</description>
    <pubDate>Thu, 27 Oct 2011 18:56:54 GMT</pubDate>
    <dc:creator>hharvey</dc:creator>
    <dc:date>2011-10-27T18:56:54Z</dc:date>
    <item>
      <title>Multiple lines are getting stuck together at indexing</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Multiple-lines-are-getting-stuck-together-at-indexing/m-p/86997#M18063</link>
      <description>&lt;P&gt;I am indexing a file of single line log events and some lines are getting chunked together into one event. Trying to figure out how to correct it.&lt;/P&gt;

&lt;P&gt;Here's some example log data that is getting indexed together in each event:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;a1-server1 App-&amp;gt; 2011-10-05 12:35:23 - a1-server1 - [99.99.99.99] user3(Active Directory Users)[gg-group] - Key Exchange number 23 occured for user with NCIP 192.168.212.63 
a1-server1 App-&amp;gt; 2011-10-05 12:35:23 - a1-server1 - [99.99.99.99]  user4(Active Directory Users)[gg-group] - Key Exchange number 5 occured for user with NCIP 192.168.212.221 
a1-server1 App-&amp;gt; 2011-10-05 12:35:23 - a1-server1 - [99.99.99.99]  user5(Active Directory Users)[gg-group] - Key Exchange number 2 occured for user with NCIP 192.168.212.193 

a1-server1 App-&amp;gt; 2011-10-05 12:33:46 - a1-server1 - [99.99.99.99]  auser2(Active Directory Users)[gg-group] - Key Exchange number 29 occured for user with NCIP 192.168.212.139 
a1-server1 App-&amp;gt; 2011-10-05 12:33:46 - a1-server1 - [99.99.99.99]  auser1(Active Directory Users)[gg-group] - Key Exchange number 16 occured for user with NCIP 192.168.212.108 

a1-server1 App-&amp;gt; 2011-10-05 12:28:43 - a1-server1 - [99.99.99.99]  auser(Active Directory Users)[gg-group]  - Logout from 99.99.99.99 (session:ff6f38ff)
a1-server1 App-&amp;gt; 2011-10-05 12:28:43 - a1-server1 - [99.99.99.99]  auser(Active Directory Users)[gg-group]  - Closed connection after 12513 seconds, with 4502 bytes read (in 19 chunks) and 19391 bytes written (in 43 chunks)
a1-server1 App-&amp;gt; 2011-10-05 12:28:43 - a1-server1 - [99.99.99.99]  auser(Active Directory Users)[gg-group]  - Network Connect: ACL count = 833.
a1-server1 App-&amp;gt; 2011-10-05 12:28:43 - a1-server1 - [99.99.99.99]  auser(Active Directory Users)[gg-group] - Network Connect: Session ended for user with IP 192.168.212.21
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Initially, in props.conf I tried setting line_merge to false:&lt;BR /&gt;
&lt;PRE&gt;[source::source-to-break]&lt;BR /&gt;
SHOULD_LINEMERGE = false&lt;/PRE&gt;&lt;/P&gt;

&lt;P&gt;When that didn't work I tried specifying a line break before the server name at the beginning of each event:&lt;BR /&gt;
&lt;PRE&gt;[source::source-to-break]&lt;BR /&gt;
SHOULD_LINEMERGE = true&lt;BR /&gt;
BREAK_ONLY_BEFORE = a[0-9]-server[0-9]\sApp[\w'-]&amp;gt;\s&lt;/PRE&gt;&lt;/P&gt;

&lt;P&gt;But that also is not working. I'm beginning to think this has something to do w/ the time, but not sure.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 09:56:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Multiple-lines-are-getting-stuck-together-at-indexing/m-p/86997#M18063</guid>
      <dc:creator>hharvey</dc:creator>
      <dc:date>2020-09-28T09:56:59Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple lines are getting stuck together at indexing</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Multiple-lines-are-getting-stuck-together-at-indexing/m-p/86998#M18064</link>
      <description>&lt;P&gt;Try the stanza below:&lt;BR /&gt;
[source::source-to-break]&lt;BR /&gt;
TIME_PREFIX = a\d+\-server\d+\s+App\-\&amp;gt;\s+&lt;BR /&gt;
TIME_FORMAT = %Y-%m-%d %H:%M:%S&lt;BR /&gt;
MAX_TIMESTAMP_LOOKAHEAD = 20&lt;BR /&gt;
LINE_BREAKER = ([\r\n]+)(?=a\d+\-server\d+\s+App\-\&amp;gt;\s+\d+\-\d+\-\d+\s+)&lt;BR /&gt;
SHOULD_LINEMERGE = false&lt;/P&gt;

&lt;P&gt;This will attempt to break right before a1-server1, extract the timestamp and format it properly. If this works please do not forget to vote &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 09:57:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Multiple-lines-are-getting-stuck-together-at-indexing/m-p/86998#M18064</guid>
      <dc:creator>_d_</dc:creator>
      <dc:date>2020-09-28T09:57:08Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple lines are getting stuck together at indexing</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Multiple-lines-are-getting-stuck-together-at-indexing/m-p/86999#M18065</link>
      <description>&lt;P&gt;took me a while to get this implemented, but I just did and it worked. thanks so much!&lt;/P&gt;</description>
      <pubDate>Thu, 27 Oct 2011 18:56:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Multiple-lines-are-getting-stuck-together-at-indexing/m-p/86999#M18065</guid>
      <dc:creator>hharvey</dc:creator>
      <dc:date>2011-10-27T18:56:54Z</dc:date>
    </item>
  </channel>
</rss>

