Calculate your consumption of Log Management and Analytics - Retain (DPS)

Latest Dynatrace
Concept
6-min read
Published Aug 12, 2025

Log - Retain feature overview

This page describes how the Log Management & Analytics - Retain DPS capability is consumed and billed. For an overview of the capability, including its main features, see Log Management & Analytics - Retain.

The usage of Distributed Tracing Distributed Tracing and Services Services is included with Dynatrace. No consumption is generated by these apps.

How consumption is calculated: GiB-day

Retained data is the amount of data saved to storage after data parsing, enrichment, transformation, and filtering but before compression. It is calculated per gibibyte-day (GiB-day).

Calculate your consumption

Apply the following calculation to determine your daily consumption for the Retain data-usage dimension:

consumption per day = (volume of uncompressed logs stored in GiB) x (GiB-day price for Retain on your rate card)

View your consumption

This section describes the different Dynatrace tools that you can use to track consumption and costs.

View your consumption with Metrics

Dynatrace provides a built-in usage metric that helps you understand and analyze your organization's consumption of Log Management and Analytics - Retain. To use this metric, in Data Explorer, enter DPS in the Search field.

Log Management and Analytics usage - Retain

Key: builtin:billing.log.retain.usage

Dimension: Byte

Resolution: 1 hour

Description: Number of bytes saved to storage after data parsing, enrichment, transformation, and filtering but before compression.

Example metric usage: monitor the total number of bytes scanned in hourly intervals

You can monitor the total bytes stored for Retain in hourly intervals for any selected timeframe using the metric builtin:billing.log.retain.usage. The example below shows usage aggregated in 1-hour intervals between 2023-09-04 and 2023-09-11 (last 7 days).

Log Management & Analytics (DPS)

View consumption with DQL queries

Example metric usage: monitor the total number of gibibytes scanned

The following DQL query provides the hourly Retain usage by bucket.

fetch dt.system.events
| filter event.kind == "BILLING_USAGE_EVENT" and event.type == "Log Management & Analytics - Retain"
| summarize {usage.event_bucket = takeLast(usage.event_bucket), billed_bytes = takeLast(billed_bytes)}, by:{billing_period = bin(timestamp, 1h), event.id}
| fieldsAdd bytes_and_bucket = record(bucket = usage.event_bucket, billed_bytes = billed_bytes)
| summarize {`total billed_bytes` = sum(billed_bytes), `billed_bytes by bucket` = collectDistinct(bytes_and_bucket)}, by:{billing_period}
| fields billing_period, `total billed_bytes`, `billed_bytes by bucket`

View consumption and costs in Account Management

You can also view usage metrics in Account Management. Go to Account Management > Subscription > Overview > Cost and usage details > Usage summary and select the Log Management and Analytics - Retain capability.

View consumption and costs via API

You can query metrics via the Environment API - Metrics API v2.