<?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: Indexer cluster ignores TRUNCATE for splunk_python in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-cluster-ignores-TRUNCATE-for-splunk-python/m-p/756653#M120011</link>
    <description>&lt;P&gt;Your point is right.&lt;BR /&gt;I have also thought that truncation can appear only on IDXC layer but it were my SHCs.&lt;/P&gt;</description>
    <pubDate>Fri, 19 Dec 2025 13:54:19 GMT</pubDate>
    <dc:creator>NoSpaces</dc:creator>
    <dc:date>2025-12-19T13:54:19Z</dc:date>
    <item>
      <title>Indexer cluster ignores TRUNCATE for splunk_python</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-cluster-ignores-TRUNCATE-for-splunk-python/m-p/756651#M120009</link>
      <description>&lt;P&gt;Have a nice day, everyone!&lt;BR /&gt;For continuous event truncation tracking, I have a simple alert that notifies me about truncation:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index="_internal" sourcetype="splunkd" log_level="WARN" "Truncating"
| rex field=_raw "limit\s+of\s+(?&amp;lt;Limit&amp;gt;\d+)\s"
| rex field=_raw "length\s+&amp;gt;=\s+(?&amp;lt;MessageLength&amp;gt;\d+)\s+"
| rex field=_raw "data_host=\"(?&amp;lt;Host&amp;gt;.*?)\",\s"
| rex field=_raw "data_sourcetype=\"(?&amp;lt;Sourcetype&amp;gt;.*?)\""
| stats count by Sourcetype, Host, Limit, MessageLength
| top limit=5 Sourcetype, MessageLength
| table Sourcetype, MessageLength&lt;/LI-CODE&gt;&lt;P&gt;After my last update, I have started to notice that the 'splunk_python' sourcetype hits the default TRUNCATE value a couple of times per hour.&lt;BR /&gt;Overall, the events look fine, so I decided to tune the TRUNCATE value on the indexer cluster layer (manager-apps\_cluster\local\props.conf):&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[splunk_python]
SHOULD_LINEMERGE = false
TRUNCATE = 20000&lt;/LI-CODE&gt;&lt;P&gt;Unfortunately, it also didn't help, and I'm still getting alerts with the default message length (10000). Then I set TRUNCATE to 0 and found no difference. What am I doing wrong?&lt;/P&gt;</description>
      <pubDate>Fri, 19 Dec 2025 13:03:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-cluster-ignores-TRUNCATE-for-splunk-python/m-p/756651#M120009</guid>
      <dc:creator>NoSpaces</dc:creator>
      <dc:date>2025-12-19T13:03:05Z</dc:date>
    </item>
    <item>
      <title>Re: Indexer cluster ignores TRUNCATE for splunk_python</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-cluster-ignores-TRUNCATE-for-splunk-python/m-p/756652#M120010</link>
      <description>&lt;P&gt;Make sure you're setting the TRUNCATE value on the Host that is reporting the truncation.&amp;nbsp; Be sure that Splunk instance is restarted after making the change.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Dec 2025 13:28:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-cluster-ignores-TRUNCATE-for-splunk-python/m-p/756652#M120010</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2025-12-19T13:28:00Z</dc:date>
    </item>
    <item>
      <title>Re: Indexer cluster ignores TRUNCATE for splunk_python</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-cluster-ignores-TRUNCATE-for-splunk-python/m-p/756653#M120011</link>
      <description>&lt;P&gt;Your point is right.&lt;BR /&gt;I have also thought that truncation can appear only on IDXC layer but it were my SHCs.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Dec 2025 13:54:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-cluster-ignores-TRUNCATE-for-splunk-python/m-p/756653#M120011</guid>
      <dc:creator>NoSpaces</dc:creator>
      <dc:date>2025-12-19T13:54:19Z</dc:date>
    </item>
  </channel>
</rss>

