Application and Infrastructure Monitoring (Host Units)

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 (that is 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 (that is 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 (that is 1 host unit) running for a full day consumes 24 host unit hours.

Serverless functions

Note: AWS CloudWatch, Azure Monitor and AWS Lambda tracing integrations consume DDUs. For more information see DDUs for serverless monitoring.

Azure Functions tracing integration

For OneAgent Azure Functions integration, Dynatrace supports the Dedicated (App Service) plan, which consumes hosts units.

The Azure Functions Consumption Plan is currently not supported.

Serverless compute services

Dynatrace OneAgent integrations for serverless compute services consume host units. For example:

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 peak rolling 4-hour average MSU values of the most recent month from IBM System Management Facility (SMF) data per monitored Logical Partitions (LPARs) or products.

The peak rolling 4-hour average MSU values can be derived from Dynatrace (per monitored LPAR) or from section P5 of SCRT report.

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.