Calculate your consumption of Traces - Query (DPS)
- Latest Dynatrace
- Concept
- 6-min read
- Published Aug 12, 2025
This page describes how the Traces - Query DPS capability is consumed and billed. For an overview of the capability, including its main features, see Traces - Query.
How consumption is calculated: GiB scanned
Query is the volume of data scanned during a DQL query's execution, whether executed directly or via an app. It is calculated per gibibyte scanned during query execution (GiB scanned).
Calculate consumption
Query usage is based on the volume of uncompressed span data that is scanned during the execution of a DQL query. Apply the following calculation to determine the maximum potential consumption of a single query execution:
(GiB of uncompressed data read during query execution) * (GiB-scanned price as per your Rate Card) = consumption
View consumption
On the environment level, Dynatrace provides pre-made Notebooks for each DPS capability that you can use for detailed analysis. These are available in Account Management (Subscription > Overview > Cost and usage details > Select the capability > Actions > Open details with Notebooks > Select or create Notebook).
The following chart shows query usage over time. It allows you to see peaks and outliers, which can guide further investigation to optimize queries and their usage.
The following chart shows query usage organized by user. You can drill down this data and see a breakdown of the apps where a given user executes queries.
To proactively manage query consumption, you can create notifications that are triggered by extensive query usage at the app or user level.