Built for scale. Priced for reality.

Metrics billable series is calculated based on two components: active series and data points per minute (DPM). By understanding these components, you’ll be able to better manage usage and reduce costs for your organization. See pricing docs –>

Yes, we provide volume discounts for enterprise-scale usage. Contact us for more details.

Yes, we have additional retention options available. Contact us for more details. Default retention is 30 days, and you can also use logs export to retain logs in your own storage bucket.

Yes, we provide volume discounts for enterprise-scale usage. Contact us for more details.

Yes, we have additional retention options available. Contact us for more details.

Yes, we provide volume discounts for enterprise-scale usage. Contact us for more details.

Yes, we have additional retention options available. Contact us for more details.

Yes, we provide volume discounts for enterprise-scale usage. Contact us for more details.

An Host is a physical or virtual operating system instance that is sending observability signals including k8s metrics - a host is considered active if it has sent observability signals in the last 15 minutes. Billable host hours is the total number of host hours measured during the month. Note: By billing based on host hours, customers don’t have to pay for their peak (i.e. 99th percentile) host usage but rather the actual host hours consumed during the billing month.

Host Hours based pricing is only applicable for customers that are using the Kubernetes Monitoring product offering in Grafana Cloud.

Yes, we provide volume discounts for enterprise-scale usage. Contact us for more details.

An Host is a physical or virtual operating system instance that is sending observability signals including traces and span metrics - a host is considered active if it has sent observability signals in the last 15 minutes. Billable host hours is the total number of host hours measured during the month.

Note: By billing based on host hours, customers don’t have to pay for their peak (i.e. 99th percentile) host usage but rather the actual host hours consumed during the billing month.

Host Hours based pricing is only applicable for customers that are using the Application Observability product offering in Grafana Cloud.

For customers not using the Application Observability product offering in Grafana Cloud and instead building their own dashboards, alerts, and workflows to monitor applications, standard pricing for Grafana Cloud Metrics, Logs, Traces, Profiles and Visualization applies and there are no charges based on Host Hours.

Yes, we provide volume discounts for Enterprise scale usage. Contact us for more details.

A “session” is defined as the time that a user is spending in a frontend application on and off from start to finish or timeout. A user session is either created or resumed when a user visits and uses the site. A user session ends after a maximum lifetime of 4 hours or after inactivity timeout of 15 minutes. The SDK will automatically create a new user session in any of these situations, if the user returns.

Yes, we provide volume discounts for enterprise-scale usage. Contact us for more details.

A test execution is a Synthetic test running in a probe location per minute of run time. Example: A synthetic test running in 5 locations that takes 1.5 minutes to complete will consume 10 executions each time it runs.

To estimate the number of test executions per month, you will need the following inputs:

• Number of Locations (Probes)
• Number of Targets (Tests)
• Duration of Test (rounded to the nearest minute)
• Frequency of Tests (in Minutes)

Yes, we provide volume discounts for enterprise-scale usage. Contact us for more details.

A test execution is a Synthetic test running in a probe location per minute of run time. Example: A synthetic test running in 5 locations that takes 1.5 minutes to complete will consume 10 executions each time it runs.

MultiHTTP checks are like HTTP checks but you can test multiple URLs in a single check to validate multi-step user flows. k6 scripted checks are like MultiHTTP checks, but you can write the checks in code instead of via a form-based approach.

To estimate the number of test executions per month, you will need the following inputs:

• Number of Locations (Probes)
• Number of Targets (Tests)
• Duration of Test (rounded to the nearest minute)
• Frequency of Tests (in Minutes)

Yes, we provide volume discounts for enterprise-scale usage. Contact us for more details.

VUh is calculated by using the following formula:

(Maximum number of VUs x test execution duration in minutes) / 60 minutes = VUh

If your test ramps up to a maximum of 100 VUs and runs for 10 minutes, the test run will use 16.67 VUh ((100 VUs x 10 minutes)/60 = 16.67 VUh).

Note that VU hours are calculated based on the period that the test run executes, not the preconfigured test duration. If the test duration is 2 or more hours but runs for only 30.01 minutes, then the subscription will be charged for the test-execution period rounded up to the next minute (in this case, 31 minutes).

The minimum for a test is 1 VUh. Find additional details here.

Yes, we provide volume discounts for enterprise-scale usage. Contact us for more details.

Any user that logs into Grafana during the billing month is considered an active user.

Enterprise plugins are a paid add-on for the Cloud Pro Pay As You Go Plan that is priced at $55 per active user per month. By default, your account will have Grafana without Enterprise plugins, which is priced at $8 per active user per month.

Yes, we provide volume discounts for enterprise-scale usage. Contact us for more details.

Any user that logs into Grafana during the billing month is considered an active user.

Enterprise plugins are a paid add-on for the Cloud Pro Pay As You Go Plan that is priced at $55 per active user per month. By default, your account will have Grafana without Enterprise plugins, which is priced at $8 per active user per month.

Yes, we provide volume discounts for enterprise-scale usage. Contact us for more details.

An active IRM user is defined as a user who is included in OnCall schedules or escalation chains or performs any of the following actions:

• Changed the status of an alert group or OnCall configuration
• Received a page or paged another user
• Created, edited, or updated an incident

Yes, we provide volume discounts for enterprise-scale usage. Contact us for more details.