Splunk® Phantom (Legacy)

Administer Splunk Phantom

Acrobat logo Download manual as PDF

Splunk Phantom 4.10.7 is the final release of Splunk's Security Orchestration, Automation, and Response (SOAR) system to be called Splunk Phantom. All later versions are named Splunk SOAR (On-premises). For more information, see the Splunk SOAR (On-premises) documentation.
Acrobat logo Download topic as PDF

Set the global action concurrency limit

The global action concurrency limit designates the maximum number of concurrent actions across all assets on the Splunk Phantom platform. When changing the global action limit, ensure the existing action limit on assets is within the new global limit. Use caution when changing this limit as it can significantly affect performance. In a cluster setup, the global action limit applies per node.

To change this limit:

  1. From the Splunk Phantom main menu, select Administration.
  2. Click Administration Settings > Environment Settings.
  3. Enter your desired action limit in the box. Use caution when changing this limit because doing so can have a significant effect on performance.
  4. Click Save Changes.

For information on setting concurrent actions for a specific asset, see Set the concurrent action limit. For information on disabling action concurrency see, Disable action lock or action concurrency.

Last modified on 08 October, 2020
Set global environment variables
Add tags to objects in Splunk Phantom

This documentation applies to the following versions of Splunk® Phantom (Legacy): 4.10, 4.10.1, 4.10.2, 4.10.3, 4.10.4, 4.10.6, 4.10.7

Was this documentation topic helpful?

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