<?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: event splitting in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/event-splitting/m-p/80096#M16481</link>
    <description>&lt;P&gt;you may want to post more information on the specifics of the problem you're observing, I don't know that we'll be able to do much to help you without understanding what is already in props.conf and examples of the behavior in the form of sample event data.&lt;/P&gt;</description>
    <pubDate>Tue, 28 Feb 2012 17:47:33 GMT</pubDate>
    <dc:creator>jbsplunk</dc:creator>
    <dc:date>2012-02-28T17:47:33Z</dc:date>
    <item>
      <title>event splitting</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/event-splitting/m-p/80094#M16479</link>
      <description>&lt;P&gt;Other than props.conf, is there any other file that controls how multi-line events are split or kept together? We are having some strange issues where an event is bundled together with lines that correspond to another event on one day and then the next day having that same event type split up incorrectly in to many chunks of lines. No configuration changes have taken place in between these two occurrences so this is really odd.&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 28 Feb 2012 02:05:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/event-splitting/m-p/80094#M16479</guid>
      <dc:creator>romantercero</dc:creator>
      <dc:date>2012-02-28T02:05:57Z</dc:date>
    </item>
    <item>
      <title>Re: event splitting</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/event-splitting/m-p/80095#M16480</link>
      <description>&lt;P&gt;Line breaking is defined in props.conf, there aren't other config files that would instruct Splunk on how to deal with the data. &lt;/P&gt;</description>
      <pubDate>Tue, 28 Feb 2012 17:45:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/event-splitting/m-p/80095#M16480</guid>
      <dc:creator>jbsplunk</dc:creator>
      <dc:date>2012-02-28T17:45:39Z</dc:date>
    </item>
    <item>
      <title>Re: event splitting</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/event-splitting/m-p/80096#M16481</link>
      <description>&lt;P&gt;you may want to post more information on the specifics of the problem you're observing, I don't know that we'll be able to do much to help you without understanding what is already in props.conf and examples of the behavior in the form of sample event data.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Feb 2012 17:47:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/event-splitting/m-p/80096#M16481</guid>
      <dc:creator>jbsplunk</dc:creator>
      <dc:date>2012-02-28T17:47:33Z</dc:date>
    </item>
  </channel>
</rss>

