Calculate Dynatrace monitoring consumption

Dynatrace monitoring consumption is based on various types of monitoring units that are consumed by your Dynatrace environment during the monitoring of your applications and related services. Details of these monitoring unit types and how these units are consumed are outlined below.

Unless otherwise stated, the consumption details explained here apply to both SaaS and Managed deployments. To get started using Dynatrace, contact Dynatrace Sales. Your sales representative will provide you with further details.

This page is provided for informational purposes only. The terms of the Dynatrace free trial offer and/or your Dynatrace license will be applied to any use of Dynatrace products or services.

Application and infrastructure monitoring

Dynatrace application and infrastructure monitoring is provided via installation of a single Dynatrace OneAgent on each monitored host in your environment. OneAgent is licensed on a per-host basis (virtual or physical server).

However, not all hosts are of equal size. Larger hosts consume more host units than do smaller-sized hosts. We use the amount of RAM on a monitored server as a measuring stick to determine the size of a host (i.e., how many host units it comprises). The advantage of this approach is its simplicity—we don’t take technology-specific factors into consideration (for example, the number of JVMs or the number of microservices that are hosted on a server). It doesn't matter if a host is .NET-based, Java-based, or something else. You can have 10 JVMs or 1,000 JVMs; such factors don't affect the amount of monitoring that an environment consumes.

OneAgent can operate in two different modes. By default, OneAgent operates in full-stack mode. Alternatively, you can use cloud-infrastructure mode to monitor hosts that don't require full-stack visibility. Cloud infrastructure mode consumes fewer host units than full-stack mode.

Host units

Refer to the host unit weighting table below to see how many host units are consumed based on the amount of RAM a monitored server has.

Max. RAM Host units (Full-stack*) Host units (Cloud infrastructure**)
1.6 GB 0.10 0.03
4 GB 0.25 0.075
8 GB 0.50 0.15
16 GB 1.0 0.3
32 GB 2.0 0.6
48 GB 3.0 0.9
64 GB 4.0 1.0
80 GB 5.0 1.0
96 GB 6.0 1.0
112 GB 7.0 1.0
nx16 GB n 1.0

* When the amount of RAM on a host falls between the values listed in the table above, the number is rounded up. For example, a host with 12 GB RAM consumes 1 host unit because 12 GB falls between 8 GB and 16 GB.
** For cloud-infrastructure monitoring mode, the same rounding principle applies, but the number of host units consumed by a host is capped at 1.0. If you have an existing agreement that doesn't reflect the 1.0 cap on host units per host, please contact your Dynatrace Sales representative.

Total host-unit consumption is calculated based on the sum of all host units of all modes and monitored systems.

Host unit hours

A host unit hour represents the consumption of a host unit over a time period. 1 host unit hour equates to 1 host unit being consumed for 1 hour. A host with 16 GB of RAM (i.e., 1 host unit) running for a full day consumes 24 host unit hours.

Digital Experience Management

In addition to the application and infrastructure monitoring provided by OneAgent, you may also require Dynatrace Synthetic Monitoring, Real User Monitoring, and Session Replay. These capabilities are consumed based on Digital Experience Management units, otherwise known as DEM units. The amount of DEM units you need depends on how many synthetic monitors you want to run and how many user sessions you need to monitor. The table below explains the rate at which DEM units are consumed per each capability type and unit of measure.

Unit of measure Capability Consumption per unit of measure
Synthetic action Browser monitors, browser clickpaths 1.0 DEM
Synthetic request HTTP monitor 0.1 DEM
User session* Real User Monitoring (Session Replay disabled) 0.25 DEM
User session* Real User Monitoring (Session Replay enabled) 1.0 DEM

* Only the user sessions of real users are counted in your consumption of user sessions. The user sessions of synthetic users and "robots" aren't counted when calculating your monitoring consumption.

Log Monitoring

Custom metrics

Limited custom metric ingestion and analysis is included in out-of-the-box Dynatrace technology support. To arrange for additional custom metric ingestion and analysis, contact Dynatrace Sales. For full details on setup and consumption of custom metrics within Dynatrace, see Custom metric ingestion and analysis.

If you have multiple Dynatrace SaaS environments under a single Dynatrace account, your free tier of custom metrics will be evenly distributed across your monitored environments.

Mainframe monitoring on IBM z/OS

Code modules running on IBM z/OS (CICS & IMS) are licensed separately based on MSUs and don't contribute to the consumption of host units or host unit hours.

The number of license MSUs needs to match the cumulative MSU capacity of the Dynatrace-instrumented CICS or IMS regions. Dynatrace doesn't provide a MSU consumption/metric. Therefore, consumption needs to be assessed manually via SMF records.