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!

Dashboards: Hiding charts while search is being executed and other uses for tokens

There are a couple of features of SimpleXML / Classic dashboards that can be used to enhance the user ...

Splunk Observability Cloud's AI Assistant in Action Series: Explaining Metrics and ...

This is the fourth post in the Splunk Observability Cloud’s AI Assistant in Action series that digs into how ...

Brains, Bytes, and Boston: Learn from the Best at .conf25

When you think of Boston, you might picture colonial charm, world-class universities, or even the crack of a ...