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

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

Retain with Included Queries feature overview

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

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).

Here's what's included with the Retain with Included Queries data-usage dimension:

Concept

Explanation

Data availability

Retained data is accessible for analysis and querying until the end of the retention period.

Retention periods

Choose a desired retention period. For log buckets, the available retention period ranges from 1 day to 10 years.

Metrics retention is defined at the bucket level, ensuring tailored retention periods for specific metrics.

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

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

Track your consumption

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

Track 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 with Included Queries. 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 usage.

The example below shows usage aggregated in 1-hour intervals between 2024-09-15 and 2024-10-15 (last 30 days).

Retain with included Queries (LMA)

View consumption with DQL queries

Example metric usage: monitor the total number of gibibytes retained per bucket

The following DQL query provides an overview of the Log Management & Analytics – Retain with Included Queries hourly usage in gibibytes retained by bucket:

fetch dt.system.events
| filter event.kind == "BILLING_USAGE_EVENT" and event.type == "Log Management & Analytics - Retain with Included Queries"
| summarize {usage.bucket = takeLast(usage.bucket), billed_bytes = takeLast(billed_bytes)}, by:{billing_period = bin(timestamp, 1h), event.id}
| fields billing_period, billed_bytes, usage.bucket
| makeTimeseries max(billed_bytes), by:{usage.bucket}, time: billing_period, interval:1h

The example below shows the hourly usage visualized in a bar chart for the last 30 days:

Retain with included Queries (LMA)

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 with Included Queries capability.

View consumption and costs via API

You can query this metric via the Environment API - Metrics API v2.

Frequently asked questions (FAQs)

Yes, the retention period for log buckets ranges from a minimum of 10 days to a maximum of 35 days. If you need to retain your data for more than 35 days, consider switching to our usage-based model with Retain, and Query.

How do I know how much query usage I have available?

The data volume stored in a bucket configured for Retain with Included Queries defines the query volume that is included in your Retain with Included Queries consumption.

Included query usage per day = (GiB of logs retained) × 15