<?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: JSON is truncated in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Why-is-JSON-getting-truncated/m-p/588795#M76320</link>
    <description>&lt;P&gt;Where do I put the props.conf file on a windows system?&lt;/P&gt;</description>
    <pubDate>Fri, 11 Mar 2022 18:36:43 GMT</pubDate>
    <dc:creator>davedoucette</dc:creator>
    <dc:date>2022-03-11T18:36:43Z</dc:date>
    <item>
      <title>Why is JSON getting truncated?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Why-is-JSON-getting-truncated/m-p/57697#M3431</link>
      <description>&lt;P&gt;Hi together,&lt;/P&gt;
&lt;P&gt;I am trying to get data via REST API input, but I'am getting this message in splunkd.log:&lt;/P&gt;
&lt;P&gt;&lt;CODE&gt;Truncating line because limit of 10000 has been exceeded with a line length &amp;gt;= 62248&lt;/CODE&gt;&lt;/P&gt;
&lt;P&gt;It seems to be that my JSON file is to long/big.&lt;/P&gt;
&lt;P&gt;When I take a look into splunk, I can see my JSON which is cut off in the middle. This is still a problem, because the JSON is no longer well-formed and cannot longer pre-processed.&lt;/P&gt;
&lt;P&gt;Is there a better way to get long JSON data in? (without setting line length limit because I have got some other JSONs which a much longer than my test request)&lt;/P&gt;
&lt;P&gt;Best regards&lt;BR /&gt;Steffen&lt;/P&gt;</description>
      <pubDate>Fri, 11 Mar 2022 19:21:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Why-is-JSON-getting-truncated/m-p/57697#M3431</guid>
      <dc:creator>tcoq</dc:creator>
      <dc:date>2022-03-11T19:21:55Z</dc:date>
    </item>
    <item>
      <title>Re: JSON is truncated</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Why-is-JSON-getting-truncated/m-p/57698#M3432</link>
      <description>&lt;P&gt;tcoq,&lt;/P&gt;

&lt;P&gt;you can create a props.conf with this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[yourjsonsourcetypehere]
TRUNCATE = 999999
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This should work for any json logs you throw in.&lt;/P&gt;

&lt;P&gt;However, I wonder...   are your logs linebreaking properly?  It's not often that I see json events that are that long.&lt;/P&gt;</description>
      <pubDate>Tue, 10 Sep 2013 19:43:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Why-is-JSON-getting-truncated/m-p/57698#M3432</guid>
      <dc:creator>mloven_splunk</dc:creator>
      <dc:date>2013-09-10T19:43:22Z</dc:date>
    </item>
    <item>
      <title>Re: JSON is truncated</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Why-is-JSON-getting-truncated/m-p/57699#M3433</link>
      <description>&lt;P&gt;You may try TRUNCATE = 0. Details:&lt;/P&gt;

&lt;P&gt;TRUNCATE = &lt;NON-NEGATIVE integer=""&gt;&lt;BR /&gt;
* Change the default maximum line length (in bytes).&lt;BR /&gt;
* Although this is in bytes, line length is rounded down when this would&lt;BR /&gt;
  otherwise land mid-character for multi-byte characters.&lt;BR /&gt;
* Set to 0 if you never want truncation (very long lines are, however, often a sign of&lt;BR /&gt;
  garbage data).&lt;BR /&gt;
* Defaults to 10000 bytes.&lt;/NON-NEGATIVE&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Sep 2013 18:35:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Why-is-JSON-getting-truncated/m-p/57699#M3433</guid>
      <dc:creator>lpolo</dc:creator>
      <dc:date>2013-09-11T18:35:05Z</dc:date>
    </item>
    <item>
      <title>Re: JSON is truncated</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Why-is-JSON-getting-truncated/m-p/57700#M3434</link>
      <description>&lt;P&gt;Great! I switched to TRUNCATE=0 and it works!&lt;/P&gt;</description>
      <pubDate>Thu, 12 Sep 2013 12:47:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Why-is-JSON-getting-truncated/m-p/57700#M3434</guid>
      <dc:creator>tcoq</dc:creator>
      <dc:date>2013-09-12T12:47:45Z</dc:date>
    </item>
    <item>
      <title>Re: JSON is truncated</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Why-is-JSON-getting-truncated/m-p/57701#M3435</link>
      <description>&lt;P&gt;I am experiencing this same problem. But the TRUNCATE = 0 setting doesn't seem to fix the issue for me.&lt;/P&gt;

&lt;P&gt;Did you add this parameter on the Universal Forwarder, or on the Indexer?&lt;BR /&gt;
Or does it not matter?&lt;/P&gt;</description>
      <pubDate>Tue, 22 Nov 2016 08:37:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Why-is-JSON-getting-truncated/m-p/57701#M3435</guid>
      <dc:creator>napomokoetle</dc:creator>
      <dc:date>2016-11-22T08:37:28Z</dc:date>
    </item>
    <item>
      <title>Re: JSON is truncated</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Why-is-JSON-getting-truncated/m-p/588795#M76320</link>
      <description>&lt;P&gt;Where do I put the props.conf file on a windows system?&lt;/P&gt;</description>
      <pubDate>Fri, 11 Mar 2022 18:36:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Why-is-JSON-getting-truncated/m-p/588795#M76320</guid>
      <dc:creator>davedoucette</dc:creator>
      <dc:date>2022-03-11T18:36:43Z</dc:date>
    </item>
  </channel>
</rss>

