Usage and billing by source

Splunk Observability Cloud admins can monitor billing usage for the following:

• Monitor Splunk APM billing and subscription usage

• Monitor Splunk Infrastructure Monitoring subscription usage (Host plans)

• Manage Infrastructure costs and billing (Host plans)

• Monitor Splunk Infrastructure Monitoring subscription usage (DPM plans only)

• Monitor Log Observer subscription usage

• Monitor RUM subscription usage

• Monitor Splunk Synthetic Monitoring subscription usage

• Monitor parent-child subscription usage

System limits

Splunk Observability Cloud has system limits that help ensure good performance, stability, and reliability. Exceeding these limits might degrade your experience.

If you exceed your ingestion limits you might incur in overcost. To help avoid overage fees, create a detector to proactively monitor for potential overages and receive alerts when you are nearing a subscription limit.

Make sure you understand what’s included in your subscription. For more detailed queries about your subscription and billing, contact your Splunk Account Team.

Learn more at Per product system limits in Splunk Observability Cloud and the following docs:

• System limits for Splunk APM

• System limits for Splunk Infrastructure Monitoring

  • Data ingest can be limited at the source by Cloud providers. You can track this with the metric sf.org.num.<cloudprovidername>ServiceClientCallCountThrottles.

• Log Observer Connect limits

• System limits for Splunk RUM