Skip to main content
Splunk® Enterprise

REST API Reference Manual

Splunk® Enterprise
8.1.7
Splunk Enterprise version 8.1 will no longer be supported as of April 19, 2023. See the Splunk Software Support Policy for details. For information about upgrading to a supported version, see How to upgrade Splunk Enterprise.
This documentation does not apply to the most recent version of Splunk® Enterprise. For documentation on the most recent version, go to the latest release.

Workload management endpoint descriptions

Manage system resources for search and indexing processes.

  • Create workload pools (CPU and memory resource groups).
  • Create workload rules to grant access and prioritize workload pools.
  • Assign scheduled and ad hoc searches to workload pools.

For more information, see About workload management in the Workload Management manual.

Usage details

Review ACL information for an endpoint

To check Access Control List (ACL) properties for an endpoint, append /acl to the path. For more information see Access Control List in the REST API User Manual.

Authentication and Authorization

Username and password authentication is required for access to endpoints and REST operations.

Splunk users must have role and/or capability-based authorization to use REST endpoints. Users with an administrative role, such as admin, can access authorization information in Splunk Web. To view the roles assigned to a user, select Settings > Access controls and click Users. To determine the capabilities assigned to a role, select Settings > Access controls and click Roles.

App and user context

Typically, knowledge objects, such as saved searches or event types, have an app/user context that is the namespace. For more information about specifying a namespace, see Namespace in the REST API User Manual.

Splunk Cloud limitations

If you have a managed Splunk Cloud deployment with search head clustering and index clustering, the REST API supports access to the search head only. You can use the REST API to interact with the search head in your deployment. Using the REST API to access any other cluster member nodes is not supported. For example, index cluster management endpoints are not applicable to Splunk Cloud deployments.

Authorized users can access and configure other cluster members, including indexer, cluster manager, and license manager nodes, in the Splunk Cloud manager user interface. 


workloads/categories

https://<host>:<mPort>/services/workloads/categories

List and edit workload categories.

There are three predefined categories: search, ingest, and misc. You cannot create or delete categories. You can only edit and list them.


Authentication and Authorization

  • GET requires the list_workload_pools capability.
  • POST requires the edit_workload_pools capability.


GET

Expand

List information about workload categories.

POST

Expand

Edit workload categories.


workloads/pools

https://<host>:<mPort>/services/workloads/pools

Perform CRUD operations on workload pools.


Authentication and Authorization

  • GET requires the list_workload_pools capability.
  • POST and DELETE require the edit_workload_pools capability.


GET

Expand

List information about workload pools.

POST

Expand

Create and configure workload pools.


workloads/rules

https://<host>:<mPort>/services/workloads/rules

Perform CRUD operations on workload rules and admission rules.


Authentication and Authorization

  • GET requires the list_workload_rules capability.
  • POST and DELETE require the edit_workload_rules capability.


GET

Expand

List information about workload rules and admission rules.

POST

Expand

Create and configure a workload rule or an admission rule.

DELETE

Expand

Delete workload rules and admission rules.


workloads/config/enable

https://<host>:<mPort>/services/workloads/config/enable

Enable workload management.


Authentication and Authorization
Requires the edit_workload_pools capability.


POST

Expand

Enable workload management


workloads/config/disable

https://<host>:<mPort>/services/workloads/config/disable

Endpoint to disable workload management.


Authentication and Authorization
Requires the edit_workload_pools capability.


POST

Expand

Disable workload management


workloads/config/get-base-dirname

https://<host>:<mPort>/services/workloads/config/get-base-dirname

Get the name of the splunk parent cgroup.


Authentication and Authorization
Requires the edit_workload_pools capability.


GET

Expand

Get the name of the splunk parent cgroup.


workloads/config/preflight-checks

https://<host>:<mPort>/services/workloads/config/preflight-checks

Run Linux preflight checks for workload management.


Authentication and Authorization
Requires the list_workload_pools and edit_workload_pools capabilities.


GET

Expand

Run Linux preflight checks for workload management.


workloads/config/set-base-dirname

https://<host>:<mPort>/services/workloads/config/set-base-dirname

Set the name of the splunk parent cgroup.


Authentication and Authorization
Requires the edit_workload_pools capability.


POST

Expand

Set the name of the splunk parent cgroup.


workloads/policy/search_admission_control

https://<host>:<mPort>/services/search/workloads/policy/search_admission_control

Enable or disable admission rules.


Authentication and Authorization

  • GET requires the list_workload_policy capability.
  • POST requires the edit_workload_policy capability.


GET

Expand

List the enabled status of admission rules.

POST

Expand

Enable or disable admission rules.


workloads/status

https://<host>:<mPort>/services/workloads/status

Get information on the current status of workload management.


Authentication and Authorization
Requires the list_workload_pools capability.


GET

Expand

Get information on the current status of workload management.


Last modified on 22 September, 2021
System endpoint descriptions  

This documentation applies to the following versions of Splunk® Enterprise: 8.1.0, 8.1.1, 8.1.2, 8.1.3, 8.1.4, 8.1.5, 8.1.6, 8.1.7, 8.1.8, 8.1.9, 8.1.10, 8.1.11, 8.1.12, 8.1.13, 8.1.14


Please expect delayed responses to documentation feedback while the team migrates content to a new system. We value your input and thank you for your patience as we work to provide you with an improved content experience!

Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters