Calculate 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 Monitoring mode. Alternatively, you can use Infrastructure Monitoring mode to monitor hosts that don't require full-stack visibility. 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. Total host-unit consumption is calculated based on the sum of all host units of all modes and monitored systems.

Max. RAM Host units (Full-Stack*) Host units (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 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.

Host unit overages (optional)

If you've arranged for an allotment of host units to monitor your hosts and you're entitled to exceed this number (i.e., overages are allowed for your account), the overages will be calculated in host unit hours. For example, if you've arranged to monitor up to 10 host units (a maximum of 160 GB total RAM) and your account allows for overages, if you connect another host that equates to 2 host units you'll have 12 host units in total and will, therefore, have exceeded your quota by 2 host units. If you continue to monitor your hosts using 12 host units for a full week, you'll accrue an overage of 336 host unit hours.
2 (host units) x 24 (hours a day) x 7 (days) = 336 (host unit hours overage)
To add or remove overages from your account, contact Dynatrace Sales.

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.

Cloud service monitoring

Beginning in early 2021, all cloud services will consume DDUs. The amount of DDU consumption per service instance depends on the number of monitored metrics and their dimensions (each metric dimension results in the ingestion of 1 data point; 1 data point consumes 0.001 DDUs). The following DDU consumption estimates per service instance are based on the selection of recommended metrics only, predefined dimensions, and assumed dimension values.

Application Security Monitoring

Application Security Monitoring helps you to visualize, analyze, and monitor security vulnerabilities in your environment that are related to third-party libraries at runtime.

Dynatrace Application Security is licensed based on the consumption of Application Security units. The number of Application Security units that an environment consumes is based on the amount of RAM that a monitored server has (see the table below) and the number of hours that those Application Security units are monitored. For example, to run Application Security for a 16 GB host for one year, 9,000 Application Security units are required [1 (Application Security unit) x 365 (days) x 24 (hours) = 9,000 (Application Security units)]. See the weighting table below for details.

Application Security units can of course be consumed in addition to host-unit hours for the purposes of Full-Stack and Infrastructure Monitoring modes. For example, you can monitor the security of a host that runs on a Tomcat server that's monitored only with Dynatrace Infrastructure Monitoring. While this approach might not provide the deeper performance insights that are provided with Full-Stack Monitoring mode, it does provide powerful Dynatrace Application Security insights while saving on costs.

The allocation of Application Security units is only applicable to hosts that run supported technologies. Please contact a Dynatrace product specialist via in-product chat or reach out to your account executive to learn more.

Digital Experience Monitoring

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 Monitoring 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 per application* Real User Monitoring (Without Session Replay playback) 0.25 DEM
User session per application* Real User Monitoring session captured with Session Replay 1.0 DEM
Session property** Real User Monitoring 0.01 DEM
Action property** Real User Monitoring 0.01 DEM
Third-party synthetic result Third-party synthetic API ingestion 0.1 DEM

* User sessions are charged per application, even if a session spans multiple applications from the same domain. Only user sessions from real users are counted in your consumption of user sessions. User sessions from synthetic users and "robots" aren't counted when calculating your monitoring consumption.
** Data types for properties are weighed differently and affect billing, monitoring, as well as consumption. Short strings (fewer than 100 characters) and numeric (long strings, double, or dates) data types are counted as 1 property each. Long string data types are counted as 1 property per 100 characters.

Custom metrics

Limited custom metric ingestion and analysis is provided with out-of-the-box Dynatrace technology support in the form of included metrics per host unit. To arrange for additional custom metric ingestion and analysis, contact Dynatrace Sales.

For full details on the setup and ingestion of custom metrics in Dynatrace, see Metric ingestion.

How custom metrics affect monitoring consumption

Custom metrics typically consume Davis data units (DDUs). However custom metrics from OneAgent-monitored hosts are first deducted from your quota of included metrics per host unit, so they don't necessarily consume DDUs. For complete details, see Metric cost calculation (DDUs).

Serverless monitoring

Dynatrace monitors serverless compute technologies through integration with cloud platform providers and OneAgent integration.

Log Monitoring

Dynatrace versions 1.207 and earlier

Dynatrace versions 1.208+

To understand how Dynatrace calculates your consumption of Davis data units for the purposes of Log Monitoring, see Calculate Log Monitoring consumption.

Mainframe monitoring on IBM z/OS

Monitoring of OneAgent code modules that run on IBM z/OS (CICS, IMS, and Java) is based on the consumption of Million Service Units (MSUs). Therefore, mainframe monitoring doesn't contribute to the consumption of host units or host unit hours.

An MSU is a measurement of the amount of processing workload that an IBM mainframe performs per hour. The amount of consumed MSUs is calculated based on CPU usage, as derived from IBM System Management Facility (SMF) data per monitored Logical Partitions (LPARs), products, or regions.

Premium High Availability

The Premium High Availability deployment model is licensed separately based only on the concurrent host units limit. Premium High Availability doesn't contribute to the consumption of concurrent host units or host unit hours.