Splunk Synthetic Monitoring follows a run-based usage structure in which users purchase a monthly license with a set number of runs for each of the three check types — Browser Checks, Uptime Checks, and API Checks. A run is a single execution of a check from a particular device and location at a specific time.
As an Administrator in Splunk Synthetic Monitoring, you can monitor your run usage by monthly billing cycle by viewing the Usage Report under Administration Settings. The following steps help you find and use the Usage Report.
Navigate to the Usage Report
Follow the steps below to find the Usage Report under Administration Settings. You need to be an account administrator to access this page.
- From the landing page of Splunk Synthetic Monitoring, click the three-dot Admin Settings menu.
- In the dropdown menu, select Usage Report.
Understand the Usage Report
At the top of the Usage Report, you see the name of your plan and the start and end dates of the current billing contract.
Read the following sections for more information about the subsequent parts of the Usage Report.
Usage summary by check type
The top table of the Usage Report, titled Usage Summary by Check Type, provides a summary by check type of your monthly license, the average usage from the last 3 months, your total usage from the current billing period so far, and the projected usage for the current billing period based on current usage patterns. See the following screenshot for an example summary table.
Projected Monthly Usage is calculated by adding the current month’s total usage so far to an estimate of usage for the remainder of the month. This estimate is calculated by multiplying the total days remaining in the month by a daily average from the past 10 days.
Runs by month
The next three charts entitled Browser Runs by Month, API Requests by Month, and Uptime Runs by Month provide a visual representation of your run usage by check type over the past three months. The following screenshot is an example chart of Browser Runs by Month.
The first three columns represent the previous three billing periods: the column height represents the actual run usage for that run type in that billing period. The fourth column represents the current billing period. The blue portion of the column represents actual run usage in the current billing period so far, and the dark gray portion represents the projected usage for the remainder of the billing period, calculated by multiplying the total days remaining in the month by a daily run average from the past 10 days.
The red line on each chart represents your license limit for the specific check type. To learn more about exceeding usage limits, see Exceeding your license below.
Per-check usage summary
The table at the bottom of the Usage Report entitled Per-check Usage Summary represents the number of monthly runs for each of the checks in your Splunk Synthetic Monitoring account.
The following screenshot provides an example of the Per-check Usage Summary table:
The Estimated Monthly Runs column is calculated based on the scheduled frequency of that run, multiplied by the number of locations for which the check is set to run.
You can sort this table by check name, state (Active or Paused), and frequency, but not by estimated monthly runs. You can also filter the table by test type and by state.
Exceeding your monthly runs
Splunk Synthetic Monitoring internally tracks usage against each account’s license. The following screenshot provides an example of a chart showing recurring overages in Uptime runs. See the Splunk Synthetic Monitoring section of Specific terms for Splunk offerings to learn more about subscription limits enforcement.
