<?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: Prevent tstats from truncating large fields in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/How-to-prevent-tstats-from-truncating-large-fields/m-p/585878#M204104</link>
    <description>&lt;P&gt;"Accelerated fields have a limitation of 1024 bytes per entry, so you cannot use fields that have more than 1024 bytes"&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://dev.splunk.com/enterprise/docs/developapps/manageknowledge/kvstore/usingconfigurationfiles/" target="_blank"&gt;https://dev.splunk.com/enterprise/docs/developapps/manageknowledge/kvstore/usingconfigurationfiles/&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 21 Feb 2022 00:27:42 GMT</pubDate>
    <dc:creator>schplunk_meiste</dc:creator>
    <dc:date>2022-02-21T00:27:42Z</dc:date>
    <item>
      <title>How to prevent tstats from truncating large fields</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-prevent-tstats-from-truncating-large-fields/m-p/409584#M118160</link>
      <description>&lt;P&gt;I have an accelerated data model with a field with large strings in it.&lt;BR /&gt;When I use the spl&lt;/P&gt;
&lt;PRE&gt;&lt;CODE&gt;| data model dm_name ds_name search | table *
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;I can see the whole fields.&lt;/P&gt;
&lt;P&gt;When I use tstats:&lt;/P&gt;
&lt;PRE&gt;&lt;CODE&gt;| tstats latest (_time) as _time latest (ds_name. data) as data from datamodel=dm_name.ds_name
where (nodename = ds_name)
groupby ds_name. id prestats=true
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;the data fields are truncated.&lt;/P&gt;
&lt;P&gt;I tried to change [stats] maxvaluesize in limits.conf without success. There seems to be no such config for tstats.&lt;/P&gt;
&lt;P&gt;How can I prevent tstats from truncating large fields?&lt;/P&gt;</description>
      <pubDate>Tue, 22 Feb 2022 15:02:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-prevent-tstats-from-truncating-large-fields/m-p/409584#M118160</guid>
      <dc:creator>rhobby</dc:creator>
      <dc:date>2022-02-22T15:02:54Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent tstats from truncating large fields</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-prevent-tstats-from-truncating-large-fields/m-p/585878#M204104</link>
      <description>&lt;P&gt;"Accelerated fields have a limitation of 1024 bytes per entry, so you cannot use fields that have more than 1024 bytes"&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://dev.splunk.com/enterprise/docs/developapps/manageknowledge/kvstore/usingconfigurationfiles/" target="_blank"&gt;https://dev.splunk.com/enterprise/docs/developapps/manageknowledge/kvstore/usingconfigurationfiles/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 21 Feb 2022 00:27:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-prevent-tstats-from-truncating-large-fields/m-p/585878#M204104</guid>
      <dc:creator>schplunk_meiste</dc:creator>
      <dc:date>2022-02-21T00:27:42Z</dc:date>
    </item>
  </channel>
</rss>

