Documentationbreadcrumb arrow Grafana Cloudbreadcrumb arrow Platformbreadcrumb arrow Pricing and usagebreadcrumb arrow Synthetic Monitoring
Grafana Cloud

Synthetic Monitoring pricing

Synthetic Monitoring bills on the number of test executions you run and the type of test. API and browser test executions are billed separately.

For current rates, refer to the pricing page.

How Synthetic Monitoring is billed

Test executions are billed per 10,000, split by test type:

  • API tests include HTTP, Ping, DNS, TCP, Traceroute, Multi Step, and Scripted checks.
  • Browser tests include Browser checks.

Each executed test also generates logs, metrics, and active series, which are billed at standard Grafana Cloud rates.

Definitions

Test execution: A synthetic test running in one probe location, per minute of run time.

Active series: A time series that has received new data points within the last 30 minutes.

How usage is calculated

To estimate your monthly test executions, you need the number of probe locations, the number of checks, the duration of a test execution rounded up to the nearest minute, and the test frequency in minutes.

Apply this formula, where 43,200 is the number of minutes in a 30-day month:

text 
probes x tests x duration x (43,200 / frequency)

For example:

  • A check that runs every minute in three probe locations is three test executions per minute, or 129,600 test executions per month.
  • A check that runs every five minutes in one location and takes three minutes thirty seconds to complete is four test executions every five minutes, or 34,560 test executions per month.

Usage calculator

When you create or edit a check, the Synthetic Monitoring UI has a built-in calculator that shows the volume of test executions per month, active series, data points per minute, and log usage to expect for that check.

The Synthetic Monitoring calculator in the Grafana Cloud Edit check page, showing the approximate usage for a check

Special considerations

Public and private probes

Test executions are counted in both public and private probe locations, and billed the same way. In both cases, execution is managed by Synthetic Monitoring, and results are sent to and managed by Grafana Cloud.

Billing metrics variance

Aggregating execution counts can cause the billable amount to vary by plus or minus 0.5% from the true value. Grafana Cloud reduces the billable amount by 0.5% to avoid overbilling.

Telemetry credits for accounts created before February 13, 2026

Note

Credits for active series and logs usage apply only to Synthetic Monitoring accounts created before February 13, 2026.

Active series credit, which offsets the active series Synthetic Monitoring generates:

  • 30 active series for every 10,000 API test executions
  • 100 active series for every 10,000 Browser test executions

Logs usage credit:

  • 400 MB ingested and retained for every 10,000 Browser test executions
  • No credit for API test executions, which generate minimal log volume

View your usage

  1. In your Grafana Cloud stack, go to Cost Management and Billing > Usage.
  2. Under Product Breakdown, select Synthetic Monitoring.