Docs » Per product limits in Splunk Observability Cloud

Per product limits in Splunk Observability Cloud đź”—

When you use more than one of the following products in Splunk Observability Cloud: Splunk APM, Splunk RUM, Splunk Synthetics, and Splunk Infrastructure Monitoring, each product has its own metric time series (MTS) creation limit. You can set up metric limits alerting to manage your resource usage on a per product basis.

The following table shows per product MTS creation limits.

Note

Splunk Infrastructure Monitoring MTS creation limit includes MTS generated by Network Explorer and metrics pipeline management.

Limit name

Default limit value

MTS creations per minute per product limit

  • Splunk Infrastructure Monitoring: 6,000 or determined by your subscription

  • Splunk APM: 6,000 or determined by your subscription

  • Splunk RUM: 6,000 or determined by your subscription

  • Splunk Synthetics: 6,000 or determined by your subscription

MTS creations per minute per product limit đź”—

  • Default limit value: 6,000 or determined by your subscription.

  • Notes: Maximum number of MTS you can create per minute for each product. For example, if you create 5,500 MTS in the first minute for Infrastructure Monitoring, you can still create 5,500 more in the next minute. You can also create another 6,000 more MTS in the first minute for each other product you use.

  • Related metrics:

    Metric name

    Description

    sf.org.numMetricTimeSeriesCreatedByDatapointType

    Number of MTS generated by each product

    sf.org.limit.metricTimeSeriesCreatedPerMinute

    MTS creations per minute limit for Infrastructure Monitoring in your organization

    sf.org.apm.limit.metricTimeSeriesCreatedPerMinute

    MTS creations per minute limit for APM in your organization

    sf.org.rum.limit.metricTimeSeriesCreatedPerMinute

    MTS creations per minute limit for RUM in your organization

    sf.org.synthetics.limit.metricTimeSeriesCreatedPerMinute

    MTS creations per minute limit for Synthetics in your organization

    sf.org.numThrottledMetricTimeSeriesCreateCallsByDatapointType

    Number of MTS that each product wasn’t able to create because you significantly exceeded your per minute MTS creation limit

    sf.org.numDatapointsDroppedInTimeout

    Number of data points Infrastructure Monitoring didn’t attempt to create because your account was throttled or limited in the previous few seconds and creation was unlikely to succeed

    sf.org.apm.numDatapointsDroppedInTimeout

    Number of data points APM didn’t attempt to create because your account was throttled or limited in the previous few seconds and creation was unlikely to succeed

    sf.org.rum.numDatapointsDroppedInTimeout

    Number of data points RUM didn’t attempt to create because your account was throttled or limited in the previous few seconds and creation was unlikely to succeed

    sf.org.synthetics.numDatapointsDroppedInTimeout

    Number of data points Synthetics didn’t attempt to create because your account was throttled or limited in the previous few seconds and creation was unlikely to succeed

  • Customer impact: Each product drops new MTS exceeding the limit without returning an error. Data points for existing MTS are still accepted.