<?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:Extracted fields limit in Splunk Cloud Platform</title>
    <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/Splunk-Cloud-Extracted-fields-limit/m-p/632615#M2068</link>
    <description>&lt;P&gt;That's a good find in the docs.&amp;nbsp; I agree that changing limit to 500 should also change indexed_kv_limit to 500.&lt;/P&gt;&lt;P&gt;Yes, you should be able to change setting on the ITSI SH using ACS.&lt;/P&gt;&lt;P&gt;I still encourage you to re-think the idea of indexing so many fields.&lt;/P&gt;</description>
    <pubDate>Tue, 28 Feb 2023 16:07:26 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2023-02-28T16:07:26Z</dc:date>
    <item>
      <title>Splunk Cloud:Extracted fields limit?</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/Splunk-Cloud-Extracted-fields-limit/m-p/632444#M2058</link>
      <description>&lt;P&gt;Hi folks,&lt;/P&gt;
&lt;P&gt;I'm using Splunk Cloud and&amp;nbsp;&lt;SPAN&gt;I'm getting only 200 fields extracted or less.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;After checking &lt;A href="https://docs.splunk.com/Documentation/ITSI/4.16.0/Configure/limits.conf#:~:text=indexed_kv_limit%20%3D%20%3Cinteger%3E" target="_self"&gt;limits.conf&lt;/A&gt;&amp;nbsp;it seems like it can be increased, but not sure If I can modify it by myself.&lt;/P&gt;
&lt;P&gt;So these are my questions:&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Can I increase it using ACS?&lt;/LI&gt;
&lt;LI&gt;Is this a global change or can it be apply to a specific index?&lt;/LI&gt;
&lt;LI&gt;What is the limit for this setting? It does not specify it in the limits.conf&lt;/LI&gt;
&lt;LI&gt;Lastly, can I have performance issues by setting it to 0 or increasing it a lot?&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Thanks in advance!&lt;/P&gt;</description>
      <pubDate>Tue, 28 Feb 2023 15:04:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/Splunk-Cloud-Extracted-fields-limit/m-p/632444#M2058</guid>
      <dc:creator>splunk_luis12</dc:creator>
      <dc:date>2023-02-28T15:04:33Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Cloud:Extracted fields limit</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/Splunk-Cloud-Extracted-fields-limit/m-p/632457#M2059</link>
      <description>&lt;P&gt;That setting cannot be changed using ACS so you'll have to submit a support request.&amp;nbsp; See&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/SplunkCloud/9.0.2209/Config/ManageLimits" target="_blank"&gt;https://docs.splunk.com/Documentation/SplunkCloud/9.0.2209/Config/ManageLimits&lt;/A&gt;&lt;/P&gt;&lt;P&gt;limits.conf is global.&amp;nbsp; It affects all indexes and all apps.&lt;/P&gt;&lt;P&gt;The maximum value is unpublished so we don't know how high it can go.&amp;nbsp; Consider submitting documentation feedback to ask Splunk to include that information.&lt;/P&gt;&lt;P&gt;Yes, you absolutely can have performance issues by indexing a lot of fields.&amp;nbsp; It's one of the reasons Splunk discourages index-time field extraction.&amp;nbsp; Search-time field extraction offers more flexibility in how fields are extracted and doesn't take up storage space like index-time extraction does.&amp;nbsp; Also, the limits.conf setting for search-time extraction, &lt;FONT face="courier new,courier"&gt;limit&lt;/FONT&gt;, &lt;STRONG&gt;can&lt;/STRONG&gt; be set using ACS.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Feb 2023 01:03:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/Splunk-Cloud-Extracted-fields-limit/m-p/632457#M2059</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2023-02-28T01:03:05Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Cloud:Extracted fields limit</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/Splunk-Cloud-Extracted-fields-limit/m-p/632462#M2060</link>
      <description>&lt;P&gt;Thanks for your response.&lt;/P&gt;&lt;P&gt;I found in this &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Admin/Limitsconf#:~:text=indexed_kv_limit%20%3D%20%3Cinteger%3E" target="_self"&gt;documentation&lt;/A&gt; the following:&lt;/P&gt;&lt;P&gt;&lt;EM&gt;* The Splunk platform always uses the higher value for either setting to enforce&lt;SPAN&gt;&amp;nbsp;index-time field extraction limits.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;SPAN&gt;*If you set 'indexed_kv_limit' to "200" and 'limit' to "500", then the&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;platform limits both index-time and search-time field extraction to 500.&lt;/SPAN&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;So it means that if I increase the 'limit' value via ACS ( which seems to be possible) then the 'indexed_kv_limit' value will increase as well right?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Also, can I increase this value in a ITSI SH using ACS?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I appreciate any insight. Thanks.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Feb 2023 02:35:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/Splunk-Cloud-Extracted-fields-limit/m-p/632462#M2060</guid>
      <dc:creator>splunk_luis12</dc:creator>
      <dc:date>2023-02-28T02:35:46Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Cloud:Extracted fields limit</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/Splunk-Cloud-Extracted-fields-limit/m-p/632615#M2068</link>
      <description>&lt;P&gt;That's a good find in the docs.&amp;nbsp; I agree that changing limit to 500 should also change indexed_kv_limit to 500.&lt;/P&gt;&lt;P&gt;Yes, you should be able to change setting on the ITSI SH using ACS.&lt;/P&gt;&lt;P&gt;I still encourage you to re-think the idea of indexing so many fields.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Feb 2023 16:07:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/Splunk-Cloud-Extracted-fields-limit/m-p/632615#M2068</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2023-02-28T16:07:26Z</dc:date>
    </item>
  </channel>
</rss>

