Why is the REST API bringing back default configur... - Splunk Community

Splunk Search

The REST API seems to return default values for max_searches_per_cpu, while the btool command brings back the actual values.

| rest splunk_server=* /services/search/concurrency-settings/search 
| table *

Any thoughts?

Hi @danielbb

Strange, it matched for me OK (v8.2.7)

btool query

 splunk btool limits list --debug | grep max_searches_per_cpu

Splunk query

| rest splunk_server=* /services/search/concurrency-settings/search 
| stats max(max_searches_per_cpu) BY splunk_server

Have you recently made a change to this setting?

Get Updates on the Splunk Community!

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...

Level Up Your Workflow: Mastering Splunk Cloud Management via Terraform

Tech Talk Recap From Chaos to Control: Scaling Splunk Cloud with Infrastructure as Code Managing apps in ...