<?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: The REST API brings back default configuration values in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Why-is-the-REST-API-bringing-back-default-configuration-values/m-p/636594#M221086</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/196884"&gt;@danielbb&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Strange,&amp;nbsp;it matched for me OK (v8.2.7)&lt;/P&gt;&lt;P&gt;btool query&lt;/P&gt;&lt;PRE&gt; splunk btool limits list --debug | grep max_searches_per_cpu&lt;/PRE&gt;&lt;P&gt;Splunk query&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| rest splunk_server=* /services/search/concurrency-settings/search 
| stats max(max_searches_per_cpu) BY splunk_server&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;Have you recently made a change to this setting?&lt;/P&gt;</description>
    <pubDate>Wed, 29 Mar 2023 21:54:44 GMT</pubDate>
    <dc:creator>yeahnah</dc:creator>
    <dc:date>2023-03-29T21:54:44Z</dc:date>
    <item>
      <title>Why is the REST API bringing back default configuration values?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-is-the-REST-API-bringing-back-default-configuration-values/m-p/636584#M221085</link>
      <description>&lt;P&gt;The REST API seems to return default values for max_searches_per_cpu, while the btool command brings back the actual values.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;| rest splunk_server=* /services/search/concurrency-settings/search 
| table * &lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any thoughts?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 30 Mar 2023 14:59:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-is-the-REST-API-bringing-back-default-configuration-values/m-p/636584#M221085</guid>
      <dc:creator>danielbb</dc:creator>
      <dc:date>2023-03-30T14:59:42Z</dc:date>
    </item>
    <item>
      <title>Re: The REST API brings back default configuration values</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-is-the-REST-API-bringing-back-default-configuration-values/m-p/636594#M221086</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/196884"&gt;@danielbb&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Strange,&amp;nbsp;it matched for me OK (v8.2.7)&lt;/P&gt;&lt;P&gt;btool query&lt;/P&gt;&lt;PRE&gt; splunk btool limits list --debug | grep max_searches_per_cpu&lt;/PRE&gt;&lt;P&gt;Splunk query&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| rest splunk_server=* /services/search/concurrency-settings/search 
| stats max(max_searches_per_cpu) BY splunk_server&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;Have you recently made a change to this setting?&lt;/P&gt;</description>
      <pubDate>Wed, 29 Mar 2023 21:54:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-is-the-REST-API-bringing-back-default-configuration-values/m-p/636594#M221086</guid>
      <dc:creator>yeahnah</dc:creator>
      <dc:date>2023-03-29T21:54:44Z</dc:date>
    </item>
  </channel>
</rss>

