<?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 can we avoid the line truncating warning? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-can-we-avoid-the-line-truncating-warning/m-p/370656#M67307</link>
    <description>&lt;P&gt;from the similar posts - &lt;/P&gt;

&lt;P&gt;You should be able to add an entry to $SPLUNK_HOME/etc/system/local/props.conf similiar to this (add it specifically for the tcp:9080):&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;[ tcp:9080]&lt;BR /&gt;
 TRUNCATE = 0&lt;/CODE&gt;&lt;BR /&gt;
which would disable truncation for that log file. This overrides the default TRUNCATE value for this source.&lt;/P&gt;

&lt;P&gt;restart splunk&lt;BR /&gt;
$SPLUNK_HOME/bin&lt;BR /&gt;
./splunk restart&lt;/P&gt;

&lt;P&gt;Before:&lt;BR /&gt;
 $SPLUNK_HOME/bin/splunk cmd btool props list 'tcp:9080' | grep TRUNCATE&lt;BR /&gt;
 TRUNCATE = 10000&lt;BR /&gt;
After:&lt;/P&gt;

&lt;P&gt;$SPLUNK_HOME/bin/splunk cmd btool props list 'tcp:9080' | grep TRUNCATE&lt;BR /&gt;
 TRUNCATE = 0&lt;/P&gt;

&lt;P&gt;the setting you are looking for, see props.conf.spec:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Admin/Propsconf"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Admin/Propsconf&lt;/A&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; #******************************************************************************
 # Line breaking
 #******************************************************************************

 # Use the following attributes to define the length of a line.

 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).
  * Defaults to 10000 bytes.
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Sat, 30 Sep 2017 04:49:37 GMT</pubDate>
    <dc:creator>inventsekar</dc:creator>
    <dc:date>2017-09-30T04:49:37Z</dc:date>
    <item>
      <title>How can we avoid the line truncating warning?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-can-we-avoid-the-line-truncating-warning/m-p/370655#M67306</link>
      <description>&lt;P&gt;On the forwarder's splunkd.log, we keep getting the following warning - &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;09-29-2017 02:11:46.400 -0500 WARN  LineBreakingProcessor - Truncating line because limit of 10000 bytes has been exceeded with a line length &amp;gt;= 11636 - data_source="tcp:9080" ...
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;How can we fix it?&lt;/P&gt;</description>
      <pubDate>Sat, 30 Sep 2017 04:40:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-can-we-avoid-the-line-truncating-warning/m-p/370655#M67306</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2017-09-30T04:40:13Z</dc:date>
    </item>
    <item>
      <title>Re: How can we avoid the line truncating warning?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-can-we-avoid-the-line-truncating-warning/m-p/370656#M67307</link>
      <description>&lt;P&gt;from the similar posts - &lt;/P&gt;

&lt;P&gt;You should be able to add an entry to $SPLUNK_HOME/etc/system/local/props.conf similiar to this (add it specifically for the tcp:9080):&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;[ tcp:9080]&lt;BR /&gt;
 TRUNCATE = 0&lt;/CODE&gt;&lt;BR /&gt;
which would disable truncation for that log file. This overrides the default TRUNCATE value for this source.&lt;/P&gt;

&lt;P&gt;restart splunk&lt;BR /&gt;
$SPLUNK_HOME/bin&lt;BR /&gt;
./splunk restart&lt;/P&gt;

&lt;P&gt;Before:&lt;BR /&gt;
 $SPLUNK_HOME/bin/splunk cmd btool props list 'tcp:9080' | grep TRUNCATE&lt;BR /&gt;
 TRUNCATE = 10000&lt;BR /&gt;
After:&lt;/P&gt;

&lt;P&gt;$SPLUNK_HOME/bin/splunk cmd btool props list 'tcp:9080' | grep TRUNCATE&lt;BR /&gt;
 TRUNCATE = 0&lt;/P&gt;

&lt;P&gt;the setting you are looking for, see props.conf.spec:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Admin/Propsconf"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Admin/Propsconf&lt;/A&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; #******************************************************************************
 # Line breaking
 #******************************************************************************

 # Use the following attributes to define the length of a line.

 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).
  * Defaults to 10000 bytes.
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Sat, 30 Sep 2017 04:49:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-can-we-avoid-the-line-truncating-warning/m-p/370656#M67307</guid>
      <dc:creator>inventsekar</dc:creator>
      <dc:date>2017-09-30T04:49:37Z</dc:date>
    </item>
    <item>
      <title>Re: How can we avoid the line truncating warning?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-can-we-avoid-the-line-truncating-warning/m-p/370657#M67308</link>
      <description>&lt;P&gt;Gorgeous !!&lt;/P&gt;</description>
      <pubDate>Sat, 30 Sep 2017 21:06:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-can-we-avoid-the-line-truncating-warning/m-p/370657#M67308</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2017-09-30T21:06:53Z</dc:date>
    </item>
    <item>
      <title>Re: How can we avoid the line truncating warning?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-can-we-avoid-the-line-truncating-warning/m-p/370658#M67309</link>
      <description>&lt;P&gt;do you do this on the indexer or search head?  is the data truncated or is the display of the data truncated?&lt;/P&gt;</description>
      <pubDate>Fri, 14 Sep 2018 16:45:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-can-we-avoid-the-line-truncating-warning/m-p/370658#M67309</guid>
      <dc:creator>jfunderburg</dc:creator>
      <dc:date>2018-09-14T16:45:26Z</dc:date>
    </item>
  </channel>
</rss>

