Try it free

Calculate your consumption of Real User and Synthetic Monitoring - Query

  • Latest Dynatrace
  • Explanation
  • Published Jan 09, 2026

Early Access

This page describes how the DEM - Query capability is consumed and billed before and after Early Access.

Overview

  • DQL queries for Real User Monitoring (RUM) and Synthetic—via Notebooks, Dashboards, Workflows, Custom Applications, Service-Level Objectives, and API—are currently in Early Access. During Early Access, these queries are not billed by Dynatrace.

  • There is no separation between RUM and Synthetic data when it comes to DEM queries—both are treated the same way. When we mention DEM data on this page, we mean both RUM and Synthetic data.

Query data usage occurs when:

  • You execute DQL queries in Notebooks, Dashboards, Workflows, Custom Applications, Service-Level Objectives, and via API.

  • Dashboard tiles that are based on DEM data trigger the execution of DQL queries on refresh and include data that is not sampled automatically.

  • You perform advanced analytics with DQL that bridge operational monitoring and business intelligence.

Query data usage does not occur when DEM queries are triggered from the following native DEM apps: Synthetic, Experience Vitals, Error Inspector, Users & Sessions.

Bill DEM-related DQL queries during Early Access

Within the Early Access program, we don't bill DEM-related DQL queries for DPS SaaS customers. These DQL queries can be executed from Notebooks, Dashboards, Workflows, Service Level Objectives, or via Dynatrace API—regardless of the query timeframe.

Any query that is triggered from native Dynatrace DEM apps (Experience Vitals, Users & Sessions, Error Inspector, Synthetic app) is always free of charge, both during Early Access and after it.

Do we bill DQL queries that include several data types (DEM, traces, logs) during Early Access?

Data that originates from querying DEM-related Grail tables is not billed during Early Access. Query data that originates from traces or logs-related sources can result in consumption of corresponding DPS capabilities like Traces – Query or Log Management & Analytics – Query.

Bill DEM-related DQL queries after Early Access ends

After Early Access ends, DQL queries for DEM data will be billed using a new Digital Experience Monitoring – Query rate card item. DPS customers with the auto-add included into their contracts will be automatically billed when DEM queries reach general availability. Customers without the auto-add need to sign an amendment that includes the Digital Experience Monitoring – Query rate card item to be able to continue using DEM-related queries at general availability.

In case you have contractual questions, please reach out to your account executive. These contractual prerequisites need to be settled, otherwise DEM queries will be deactivated at general availability.

How DEM-related DQL query consumption is calculated

The volume of query data is calculated per gibibyte when scanned during a query execution (GiB scanned). Dynatrace does not bill consumption for DEM queries during Early Access.

Track your DEM-related DQL query usage

During Early Access and after it, we provide an in-product dashboard that allows you to estimate your DEM-related DQL query usage. This estimation is the basis for anticipating future billing costs. The dashboard is available directly from the DEM launchpad.

How to reduce query volume caused by DQL queries

  • Use custom metrics for frequently visited dashboards.
  • Reduce refresh rates of your dashboards.
  • Reduce query timeframes.
  • Use the sampling feature in queries.

Related topics

  • Real User and Synthetic Monitoring overview (DPS)
  • What is Dynatrace Grail?
  • License Dynatrace
  • Dynatrace Query Language
  • Dynatrace pricing
Related tags
Dynatrace PlatformDigital Experience