<?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: How does Splunk divide events? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-does-Splunk-divide-events/m-p/120118#M24985</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;To do this put the following 2 lines in forwarder's props.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;SHOULD_LINEMERGE=true
MAX_EVENTS = 2
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Regards,&lt;BR /&gt;
Ahmed Elakwah&lt;/P&gt;</description>
    <pubDate>Tue, 27 Jan 2015 23:40:42 GMT</pubDate>
    <dc:creator>aakwah</dc:creator>
    <dc:date>2015-01-27T23:40:42Z</dc:date>
    <item>
      <title>How does Splunk divide events?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-does-Splunk-divide-events/m-p/120116#M24983</link>
      <description>&lt;P&gt;There is an application putting SOAP logs, request and response, in a small delay of 0 ~10 secs into the log file - I want this to be indexed as a single event, but Splunk indexes it into 2 events - request and response separately. This doesn't always happen, but quite frequently. How can I achieve this?&lt;/P&gt;</description>
      <pubDate>Tue, 27 Jan 2015 23:30:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-does-Splunk-divide-events/m-p/120116#M24983</guid>
      <dc:creator>sylim_splunk</dc:creator>
      <dc:date>2015-01-27T23:30:36Z</dc:date>
    </item>
    <item>
      <title>Re: How does Splunk divide events?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-does-Splunk-divide-events/m-p/120117#M24984</link>
      <description>&lt;P&gt;This is not what Splunk can support. In order to get data indexed in a timely way, we presume an event is complete IF:&lt;BR /&gt;
 - The last character of the file is a newline&lt;BR /&gt;
 - The size of the file is not a multiple of 512 bytes&lt;BR /&gt;
So if your app writes out a complete line and the stops, Splunk will break it.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Jan 2015 23:35:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-does-Splunk-divide-events/m-p/120117#M24984</guid>
      <dc:creator>sylim_splunk</dc:creator>
      <dc:date>2015-01-27T23:35:13Z</dc:date>
    </item>
    <item>
      <title>Re: How does Splunk divide events?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-does-Splunk-divide-events/m-p/120118#M24985</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;To do this put the following 2 lines in forwarder's props.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;SHOULD_LINEMERGE=true
MAX_EVENTS = 2
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Regards,&lt;BR /&gt;
Ahmed Elakwah&lt;/P&gt;</description>
      <pubDate>Tue, 27 Jan 2015 23:40:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-does-Splunk-divide-events/m-p/120118#M24985</guid>
      <dc:creator>aakwah</dc:creator>
      <dc:date>2015-01-27T23:40:42Z</dc:date>
    </item>
    <item>
      <title>Re: How does Splunk divide events?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-does-Splunk-divide-events/m-p/120119#M24986</link>
      <description>&lt;P&gt;If there's a gap more than 3 seconds between each data flush, either by app or by OS the event will be indexed separately because of this behavior. To work around it increase the value of time_before_close to, like 10 secs. &lt;/P&gt;

&lt;P&gt;[monitor://D:\LogFiles\Test]&lt;BR /&gt;
time_before_close = 10&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 16:43:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-does-Splunk-divide-events/m-p/120119#M24986</guid>
      <dc:creator>sylim_splunk</dc:creator>
      <dc:date>2020-09-29T16:43:21Z</dc:date>
    </item>
  </channel>
</rss>

