<?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: Splunk Cloud HTTP-INPUT Truncating to 10000 Characters in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-set-Splunk-Cloud-HTTP-INPUT-Truncating-to-10000/m-p/585156#M102961</link>
    <description>&lt;P&gt;thanks &lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/229101"&gt;@tshah-splunk&lt;/a&gt; I'll have a look and see if I can make that change. will update with result.&lt;BR /&gt;&lt;BR /&gt;-C&lt;/P&gt;</description>
    <pubDate>Tue, 15 Feb 2022 12:03:27 GMT</pubDate>
    <dc:creator>CS_</dc:creator>
    <dc:date>2022-02-15T12:03:27Z</dc:date>
    <item>
      <title>How to set Splunk Cloud HTTP-INPUT Truncating to 10000 Characters</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-set-Splunk-Cloud-HTTP-INPUT-Truncating-to-10000/m-p/585150#M102959</link>
      <description>&lt;P&gt;Hi all,&lt;BR /&gt;&lt;BR /&gt;We are using Splunk Cloud, and I am using the &lt;A href="https://http-inputs-mydomain.com/services/collector/raw" target="_blank" rel="noopener"&gt;https://http-inputs-mydomain.com/services/collector/raw&lt;/A&gt; to send a log file for ingestion.&lt;BR /&gt;&lt;BR /&gt;The problem is that each line in this log file can be quite big, 25000 characters or more.&lt;BR /&gt;&lt;BR /&gt;Splunk Cloud is truncating at 10,000 characters.&lt;BR /&gt;&lt;BR /&gt;I can find steps for handling this on Splunk On-Prem for Heavy Log Forwarders etc. but doesn't seem to be addressed for the http-inputs on cloud.&lt;BR /&gt;&lt;BR /&gt;Any idea's on how I can change it to accept larger logs?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Chris&lt;/P&gt;</description>
      <pubDate>Wed, 16 Feb 2022 15:20:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-set-Splunk-Cloud-HTTP-INPUT-Truncating-to-10000/m-p/585150#M102959</guid>
      <dc:creator>CS_</dc:creator>
      <dc:date>2022-02-16T15:20:51Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Cloud HTTP-INPUT Truncating to 10000 Characters</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-set-Splunk-Cloud-HTTP-INPUT-Truncating-to-10000/m-p/585154#M102960</link>
      <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/242496"&gt;@CS_&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Can you try defining the TRUNCATE parameter in the props.conf file for the sourcetype that you have defined in the inputs.conf for HEC Token input. The default value of this parameter is 10000, hence the reason for truncating at 10000 characters. You can increase the value to accept larger logs.&lt;/P&gt;&lt;P&gt;More details for the parameter can be found here -&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.2.4/Admin/Propsconf" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/8.2.4/Admin/Propsconf&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Feb 2022 11:56:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-set-Splunk-Cloud-HTTP-INPUT-Truncating-to-10000/m-p/585154#M102960</guid>
      <dc:creator>tshah-splunk</dc:creator>
      <dc:date>2022-02-15T11:56:41Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Cloud HTTP-INPUT Truncating to 10000 Characters</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-set-Splunk-Cloud-HTTP-INPUT-Truncating-to-10000/m-p/585156#M102961</link>
      <description>&lt;P&gt;thanks &lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/229101"&gt;@tshah-splunk&lt;/a&gt; I'll have a look and see if I can make that change. will update with result.&lt;BR /&gt;&lt;BR /&gt;-C&lt;/P&gt;</description>
      <pubDate>Tue, 15 Feb 2022 12:03:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-set-Splunk-Cloud-HTTP-INPUT-Truncating-to-10000/m-p/585156#M102961</guid>
      <dc:creator>CS_</dc:creator>
      <dc:date>2022-02-15T12:03:27Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Cloud HTTP-INPUT Truncating to 10000 Characters</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-set-Splunk-Cloud-HTTP-INPUT-Truncating-to-10000/m-p/585255#M102976</link>
      <description>&lt;P&gt;Yes, the TRUNCATE parameter should definitely work as you are using&lt;STRONG&gt;&amp;nbsp;services/collector/raw&lt;/STRONG&gt; endpoint for HEC.&lt;/P&gt;&lt;P&gt;Just to keep in mind, the TRUNCATE parameter or any other index-time/parsing parameters will not work if you are using just the regular &lt;STRONG&gt;/services/collector&lt;/STRONG&gt; endpoint.&lt;/P&gt;</description>
      <pubDate>Wed, 16 Feb 2022 04:46:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-set-Splunk-Cloud-HTTP-INPUT-Truncating-to-10000/m-p/585255#M102976</guid>
      <dc:creator>VatsalJagani</dc:creator>
      <dc:date>2022-02-16T04:46:26Z</dc:date>
    </item>
    <item>
      <title>Re: How to set Splunk Cloud HTTP-INPUT Truncating to 10000 Characters</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-set-Splunk-Cloud-HTTP-INPUT-Truncating-to-10000/m-p/585397#M102995</link>
      <description>&lt;P&gt;We were able to get it working by amending the source type on the HEC token, and setting the character limit to 1mb (1,000,000 characters)&lt;/P&gt;</description>
      <pubDate>Wed, 16 Feb 2022 16:35:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-set-Splunk-Cloud-HTTP-INPUT-Truncating-to-10000/m-p/585397#M102995</guid>
      <dc:creator>CS_</dc:creator>
      <dc:date>2022-02-16T16:35:26Z</dc:date>
    </item>
  </channel>
</rss>

