Splunk Search

Why is the REST API bringing back default configuration values?

danielbb
Motivator

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?

 

Tags (1)
0 Karma

yeahnah
Motivator

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?

0 Karma
Get Updates on the Splunk Community!

Unlock Database Monitoring with Splunk Observability Cloud

  In today’s fast-paced digital landscape, even minor database slowdowns can disrupt user experiences and ...

Purpose in Action: How Splunk Is Helping Power an Inclusive Future for All

At Cisco, purpose isn’t a tagline—it’s a commitment. Cisco’s FY25 Purpose Report outlines how the company is ...

[Upcoming Webinar] Demo Day: Transforming IT Operations with Splunk

Join us for a live Demo Day at the Cisco Store on January 21st 10:00am - 11:00am PST In the fast-paced world ...