<?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: Events chunked into 256 lines in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Events-chunked-into-256-lines/m-p/49446#M9387</link>
    <description>&lt;P&gt;In props.conf, change MAX_EVENTS&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;MAX_EVENTS = &amp;lt;integer&amp;gt;
* Specifies the maximum number of input lines to add to any event. 
* Splunk breaks after the specified number of lines are read.
* Defaults to 256.
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Tue, 14 Sep 2010 04:24:52 GMT</pubDate>
    <dc:creator>dwaddle</dc:creator>
    <dc:date>2010-09-14T04:24:52Z</dc:date>
    <item>
      <title>Events chunked into 256 lines</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Events-chunked-into-256-lines/m-p/49445#M9386</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;

&lt;P&gt;I have the following output from a Perl script that runs every 5 mins:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;09-13-2010 16:21:20 -  Inventory Report 
DATACENTER, CLUSTER, VMHOST, VM
PPD, DNSAS-Cluster1, dnsas-esx1, dnsa-secweb1
PPD, DNSAS-Cluster1, dnsas-esx1, dnsasval1-dev9
PPD, DNSAS-Cluster1, dnsas-esx1, ddist3-dev9
PPD, DNSAS-Cluster1, dnsas-esx1, dmplupe1-dev9
PPD, DNSAS-Cluster1, dnsas-esx1, dnsasext1-dev9
...
...
...
(520 lines)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;And this is how my props.conf looks like:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source::vm_inventory]
SHOULD_LINEMERGE=True
BREAK_ONLY_BEFORE_DATE=True
TIME_FORMAT=%m-%d-%Y %H:%M:%S
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;However the events got truncated into 256 line chunks. Am I missing anything here? Or should I do it this way?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source::vm_inventory]
TRUNCATE = 0
LINE_BREAKER = (?!)
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 14 Sep 2010 04:16:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Events-chunked-into-256-lines/m-p/49445#M9386</guid>
      <dc:creator>Nicholas_Key</dc:creator>
      <dc:date>2010-09-14T04:16:12Z</dc:date>
    </item>
    <item>
      <title>Re: Events chunked into 256 lines</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Events-chunked-into-256-lines/m-p/49446#M9387</link>
      <description>&lt;P&gt;In props.conf, change MAX_EVENTS&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;MAX_EVENTS = &amp;lt;integer&amp;gt;
* Specifies the maximum number of input lines to add to any event. 
* Splunk breaks after the specified number of lines are read.
* Defaults to 256.
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 14 Sep 2010 04:24:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Events-chunked-into-256-lines/m-p/49446#M9387</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2010-09-14T04:24:52Z</dc:date>
    </item>
    <item>
      <title>Re: Events chunked into 256 lines</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Events-chunked-into-256-lines/m-p/49447#M9388</link>
      <description>&lt;P&gt;You can either set &lt;CODE&gt;MAX_EVENTS&lt;/CODE&gt; high, which will take CR-LF delimited lines and merge them up to 256 lines, &lt;EM&gt;or&lt;/EM&gt; you can use the&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;TRUNCATE = 0
LINE_BREAKER = (?!)
SHOULD_LINEMERGE = false
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;method, &lt;EM&gt;except&lt;/EM&gt; that the &lt;CODE&gt;LINE_BREAKER = (?!)&lt;/CODE&gt; will &lt;EM&gt;only&lt;/EM&gt; split an event at the end of input, i.e., it's only going to work when you get a new file, or if it's a scripted input that gets invoked once for each event. &lt;CODE&gt;SHOULD_LINEMERGE = false&lt;/CODE&gt; potentially has much better performance, but probably if you use it, you should use:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;LINE_BREAKER = ([\r\n]+)\d{2}-\d{2}-\d{4}\s+\d{1,2}:\d{2}:\d{2}
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;FURTHERMORE, I notice that you don't have a time zone specified in your timestamp, I &lt;EM&gt;strongly&lt;/EM&gt; recommend that you include the time zone in your timestamp (unless you are committed to always logging those in UTC, in which case it wouldn't hurt to include &lt;CODE&gt;Z&lt;/CODE&gt; at the end anyway).&lt;/P&gt;</description>
      <pubDate>Tue, 14 Sep 2010 06:16:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Events-chunked-into-256-lines/m-p/49447#M9388</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2010-09-14T06:16:50Z</dc:date>
    </item>
  </channel>
</rss>

