<?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: max value for truncate, max_events in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/max-value-for-truncate-max-events/m-p/135908#M27989</link>
    <description>&lt;P&gt;Are you really sure that you want a 10MB file in a single event? Actually, I'm not sure that it will really work, i.e. if there are other limitations that are non-configurable. But it's always worth a try.&lt;/P&gt;

&lt;P&gt;See the docs:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.0.3/Admin/Propsconf"&gt;http://docs.splunk.com/Documentation/Splunk/6.0.3/Admin/Propsconf&lt;/A&gt;&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 (lines).

TRUNCATE = &amp;lt;non-negative integer&amp;gt;
* Change the default maximum line length (in bytes).
* Although this is in bytes, line length is rounded down when this would
  otherwise land mid-character for multi-byte characters.
* Set to 0 if you never want truncation (very long lines are, however, often a sign of
  garbage data).
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;/K&lt;/P&gt;</description>
    <pubDate>Fri, 18 Apr 2014 09:28:26 GMT</pubDate>
    <dc:creator>kristian_kolb</dc:creator>
    <dc:date>2014-04-18T09:28:26Z</dc:date>
    <item>
      <title>max value for truncate, max_events</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/max-value-for-truncate-max-events/m-p/135907#M27988</link>
      <description>&lt;P&gt;What is the max value for truncate, max_events as my xml files size is 10Mbytes? thks. &lt;/P&gt;</description>
      <pubDate>Fri, 18 Apr 2014 03:40:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/max-value-for-truncate-max-events/m-p/135907#M27988</guid>
      <dc:creator>SplunkCSIT</dc:creator>
      <dc:date>2014-04-18T03:40:52Z</dc:date>
    </item>
    <item>
      <title>Re: max value for truncate, max_events</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/max-value-for-truncate-max-events/m-p/135908#M27989</link>
      <description>&lt;P&gt;Are you really sure that you want a 10MB file in a single event? Actually, I'm not sure that it will really work, i.e. if there are other limitations that are non-configurable. But it's always worth a try.&lt;/P&gt;

&lt;P&gt;See the docs:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.0.3/Admin/Propsconf"&gt;http://docs.splunk.com/Documentation/Splunk/6.0.3/Admin/Propsconf&lt;/A&gt;&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 (lines).

TRUNCATE = &amp;lt;non-negative integer&amp;gt;
* Change the default maximum line length (in bytes).
* Although this is in bytes, line length is rounded down when this would
  otherwise land mid-character for multi-byte characters.
* Set to 0 if you never want truncation (very long lines are, however, often a sign of
  garbage data).
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;/K&lt;/P&gt;</description>
      <pubDate>Fri, 18 Apr 2014 09:28:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/max-value-for-truncate-max-events/m-p/135908#M27989</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2014-04-18T09:28:26Z</dc:date>
    </item>
    <item>
      <title>Re: max value for truncate, max_events</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/max-value-for-truncate-max-events/m-p/135909#M27990</link>
      <description>&lt;P&gt;I had saw that and confirm that more 20K files in a single event will not work. So i need to remove certain tags in a xml also dont work becuase that particular tag are more than 20K bytes large. So how to split one event into multiple event and also to ensure all the files are forwarded to indexer?&lt;/P&gt;</description>
      <pubDate>Fri, 18 Apr 2014 11:15:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/max-value-for-truncate-max-events/m-p/135909#M27990</guid>
      <dc:creator>SplunkCSIT</dc:creator>
      <dc:date>2014-04-18T11:15:40Z</dc:date>
    </item>
    <item>
      <title>Re: max value for truncate, max_events</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/max-value-for-truncate-max-events/m-p/135910#M27991</link>
      <description>&lt;P&gt;Multiple MB in a single event do work from an indexing and searching point of view, whether it makes sense to do that depends on your use case.&lt;/P&gt;</description>
      <pubDate>Fri, 18 Apr 2014 12:40:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/max-value-for-truncate-max-events/m-p/135910#M27991</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-04-18T12:40:25Z</dc:date>
    </item>
  </channel>
</rss>

