Observability Cloud Usage, Subscription Limits Enforcement, and Entitlements

1. Subscription Limits. The service is purchased as a subscription. Each subscription plan is defined by the subscription capacity limits as described in the applicable Order (the “Subscription Limits”).

2. Usage Measurement
   

   • Splunk Infrastructure Monitoring. Splunk measures Customer’s maximum concurrent usage of each component in the Subscription Limits on an hourly basis. At the end of each month, Splunk measures the monthly usage at the average of all hourly measurements during that month (the “Infrastructure Monitoring Monthly Usage Level”). 

   • Splunk APM. Splunk measures Customer’s maximum concurrent usage of each component in the Subscription Limits on a per minute basis. At the end of each month, Splunk will calculate the average usage across all per-minute measurements of the monthly cycle, as well as 50% of the peak of all the per-minute measurements of the month. The higher value of the two will determine the usage for that month (the “APM Monthly Usage Level”).

   • Splunk RUM. Splunk measures Customer’s usage as the number of Sessions per month. At the end of each month, Splunk measures the total number of Sessions per month, during that month (the “RUM Monthly Usage Level”).

   • Splunk Log Observer. Splunk measures Customer’s usage as the volume per month of Indexed Data and Ingested Data. At the end of each month, Splunk measures the total volume used per month of Indexed Data and Ingested Data, during that month (the “Log Observer Monthly Usage Level”).

   • Splunk Synthetic Monitoring Splunk measures Customer’s usage as the total number of Browser Test Runs, API Test Runs, and Uptime Test Runs during each month (the “Synthetic Monitoring Monthly Usage Level”).

   • Splunk Web Optimization. For each pack of 1000 Enterprise Browser Test Runs purchased, Customer receives 1 Web Optimization Scan per month.

   • Splunk Incident Intelligence. Splunk measures Customer’s usage as the number of unique Active Users each calendar month (the “ Incident Intelligence Monthly Usage Level”).
     

3. Proration for Monthly Metrics. For Offerings with Capacity based on monthly metrics, the metrics will be based on calendar month measurements. Metrics will be prorated on the first and last month based on the actual subscription start date.

4. Subscription Limits Enforcement. If Customer’s Infrastructure Monitoring Monthly Usage Level, APM Monthly Usage Level, RUM Monthly Usage Level,  Log Observer Monthly Usage Level, Synthetic Monitoring Monthly Usage Level, and Incident Intelligence Monthly Usage Level (collectively, the “Monthly Usage Levels”) exceed the contractual allowable Subscription Limits, Customer agrees to pay Splunk an overage fee (the “Overage Fee”) calculated as 150% of the prices specified in the rate card below (prorated as applicable) (the “Overage Rate”), or Splunk may, at its sole discretion, limit Customer’s ability to add new monitors until it conforms to the contractual Subscription Limits, provided, however, that to help Customer avoid improperly incurring fees, if Customer’s usage at any time during the term of the General Terms significantly exceeds the Customer’s contractual Subscription Limits (as determined by Splunk at its sole discretion), Splunk may limit Customer’s ability to add new monitors, irrespective of Customer’s Monthly Usage Levels.

Splunk Infrastructure Monitoring Standard Edition

Splunk Infrastructure Monitoring Enterprise Edition

Splunk APM Standard Edition

Splunk APM Enterprise Edition

Splunk APM Standard Edition - TAPM

Splunk APM Enterprise Edition TAPM

Splunk APM Standard Edition with Profiling - TAPM

Splunk APM Enterprise Edition with Profiling - TAPM