Splunk® Enterprise

Capacity Planning Manual

Splunk Enterprise version 9.0 will no longer be supported as of June 14, 2024. See the Splunk Software Support Policy for details. For information about upgrading to a supported version, see How to upgrade Splunk Enterprise.

Splunk Enterprise service limits

The following are Splunk Enterprise service limits and constraints. These service limits are applicable to all Splunk Enterprise subscriptions. You can use this list as guidance to ensure the best experience. Keep in mind that some limits depend on configuration, system load, performance, and available resources.

Service Limit Best Practice
Number of primary buckets in the cluster Max: 40,000,000

Recommended: 25,000,000

Number of concurrent users Max: 2000

Recommended: 500

Number of peers in a non-clustered distributed search environment Max: 1000 with bestEffortSearch

Recommended: 500

Number of alert suppressions in a search head cluster Max: 100,000

Recommended: 1000

Number of search-heads in a search head cluster Max: 50

Recommended: 10

Number of sites in multisite cluster Max: 6

Recommended: 3

Last modified on 30 March, 2024
Forwarder-to-indexer ratios   Parallelization settings

This documentation applies to the following versions of Splunk® Enterprise: 8.2.0, 8.2.1, 8.2.2, 8.2.3, 8.2.4, 8.2.5, 8.2.6, 8.2.7, 8.2.8, 8.2.9, 8.2.10, 8.2.11, 8.2.12, 9.0.0, 9.0.1, 9.0.2, 9.0.3, 9.0.4, 9.0.5, 9.0.6, 9.0.7, 9.0.8, 9.0.9, 9.1.0, 9.1.1, 9.1.2, 9.1.3, 9.1.4, 9.2.0, 9.2.1

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