System limits for Splunk Infrastructure Monitoring 🔗

Splunk Infrastructure Monitoring has system limits that help ensure good performance, stability, and reliability. These limits also protect the Infrastructure Monitoring multitenant environment. Exceeding these limits might degrade your Infrastructure Monitoring experience.

To help you avoid problems when you use Infrastructure Monitoring, consider the system limit information presented in this document. Besides, there are several out-of-the-box charts in Splunk Observability Cloud for the metrics described below. Admins can view these charts by navigating to Settings > Organization Overview.

This documentation uses the following abbreviations:

Active MTS (AMTS)
Data points per minute (DPM)
Event time series (ETS)
Inactive MTS (IMTS)
Metric time series (MTS)

The tables in this document summarize limits for these product areas:

Main system limits
Charts, detectors, and SignalFlow limits
Data ingestion limits
MTS metadata limits
Time Series Window API limits
Subscription limits
Web app limits

For each limit, Splunk provides the following:

The name and value of each system limit
If available, the organization metrics associated with the limit
The impact you observe when you exceed the limit

Main system limits 🔗

Limit name	Default limit value
AMTS limit	Determined by your subscription
Maximum number of detectors per organization	1,000
Maximum number of MTS allowed per chart data() function	10,000 for standard subscriptions 30,000 for enterprise subscriptions
Maximum number of MTS per detector data() function	10,000 for standard subscriptions 30,000 for enterprise subscriptions
MTS creations per minute limit	6,000 or determined by your subscription
Number of input MTS per job	250,000

Note

In most cases, you should use the default system limits. To adjust the limit values for your org, contact Splunk Observability Cloud Support. See Splunk Observability Cloud support.

Charts, detectors, and SignalFlow limits 🔗

Limit name	Default limit value
Maximum alert rate per detector	10,000 alerts/minute for a detector with resolution smaller or equal to 1 minute 20,000 or (job resolution/1m)*10,000)) for a detector with resolution larger than 1 minute, whichever is smaller
Maximum max delay setting for SignalFlow programs	15 min
Maximum min delay setting for SignalFlow programs	15 min
Maximum number of active alerts per detector	200,000
Maximum number of allocated data points per SignalFlow program	60,000,000
Maximum number of queries per SignalFlow program	200
Maximum number of derived MTS per SignalFlow program	500,000
Maximum number of detectors per organization	1,000
Maximum number of functions and methods per SignalFlow program	1,000
Maximum number of MTS allowed per chart data() function	10,000 for standard subscriptions 30,000 for enterprise subscriptions
Maximum number of MTS analyzed across all SignalFlow programs	The larger of 10,000,000 AMTS or 20% of your total AMTS.
Maximum number of MTS per detector data() function	10,000 for standard subscriptions 30,000 for enterprise subscriptions
Maximum number of prefix wildcards per filter() function	150
Maximum number of query arguments in a filter() function	256
Maximum number of wildcards per filter() function	35
Maximum SignalFlow program stack size	64
Maximum SignalFlow program text size	50,000
Maximum SignalFlow programs per minute	1,000 SignalFlow programs per minute
Number of input MTS per job	250,000
Maximum number of SignalFlow jobs per organization	5,000 per minute
Maximum number of SignalFlow jobs per websocket connection	300

Data ingestion limits 🔗

Limit name	Default limit value
New dimension or property key name limit	40 per week
Events per minute	Determined by your subscription
MTS creations per minute limit	6,000 or determined by your subscription
MTS creations per hour limit	60 times your MTS per minute limit
MTS creations bursting per minute limit	10 times your MTS per minute limit, with a maximum of 20 minutes worth of bursting capacity in an hour.
Maximum number of API calls per minute	100,000

MTS metadata limits 🔗

Limit name	Default limit value
Dimension/Metric value length	256
Number of properties per dimension	75
Number of tags per dimension	50
Number of dimensions per MTS	36
Maximum dimension name length	128

Subscription limits 🔗

Limit name	Default limit value
AMTS limit	Determined by your subscription
Burst DPM limit	Multiples of entitlement
Bundled MTS limit	Determined by your subscription
Container burst/overage limit	Multiples of entitlement
Container entitlement	Set by your contract entitlement
Data points per minute (DPM) limit	Set by your contract entitlement
Custom MTS burst/overage limit	Multiples of entitlement
Custom MTS entitlement	Set by your contract entitlement
Host burst/overage limit	Multiples of entitlement
Host entitlement	Contract entitlement
IMTS Limit	Determined by your subscription

Time Series Window API limits 🔗

Limit name	Default limit value
timeserieswindow API data point limit	1,000,000

Web app limits 🔗

Limit name	Default limit value
Email address invitations per minute	1
Organization invitations per day	5,000
Maximum number of dashboards you can retrieve	20,000
Maximum rendered MTS for area or stacked column visualizations	500
Maximum rendered MTS for column chart visualizations	20
Maximum rendered MTS for line, histogram, or heatmap visualizations	1,000

This page was last updated on Mar 26, 2025.

Related Topics