Dynatrace Infrastructure Monitoring is a OneAgent monitoring mode that provides comprehensive host-level observability for physical and virtual machines. This page explains how Infrastructure Monitoring consumption is calculated, how to track and analyze your usage, and how to optimize your spend.
In addition to all features of Foundation & Discovery, Infrastructure Monitoring also includes detailed process performance metrics, disk performance metrics, process-to-process network analysis, and per process memory analysis. Dynatrace Extensions can be enabled on hosts with Infrastructure Monitoring mode and may consume custom metric data points.
Infrastructure Monitoring consumption is measured in host hours, using the Infrastructure Monitoring rate card item.
An operating system instance (physical or virtual machine) on which Dynatrace OneAgent is installed and running.
A single measurement value stored in Dynatrace that belongs to a metric identified by a metric key and has a timestamp.
A host hour represents one hour of active monitoring for a single host.
Consumption is independent of the host's memory size. Each monitored host contributes one host hour per hour regardless of how much RAM it has.
Dynatrace is built for dynamic cloud-native environments where hosts and services are rapidly spun up and destroyed. Therefore, billing granularity for host-hour consumption is calculated in 15-minute intervals. When a host is monitored for fewer than 15 minutes in an interval, host-hour consumption is rounded up to 15 minutes before consumption is calculated.
The figure below illustrates how host-hour consumption per host is calculated at 15-minute intervals.

This section assumes that you have followed the Dynatrace-recommended deployment options. If you implement a custom deployment, the charging of included metrics may still work as described—but this is not guaranteed by Dynatrace.
Use of Infrastructure Monitoring metrics and other built-in metrics is included at no additional cost on Infrastructure Monitoring-enabled hosts.
Every host also includes 1,500 custom metric data points in each 15-minute interval. Unused custom metric data points don't roll over to subsequent intervals.
Included metric data points are applied automatically to metrics that originate at hosts that are monitored by OneAgent in Infrastructure Monitoring mode. This applies to custom metrics as described in the table below.
Custom metric data points that exceed your included volume of metric data points are charged as Custom Metrics Classic.
| Origin | Examples (including but not limited to) |
|---|---|
An Infrastructure-monitored host and sent via the OneAgent metric API |
|
An Infrastructure-monitored Kubernetes node |
|
1 (hosts monitored) × 1,500 (metric data points) = 1,500 included custom metric data points2 (hosts monitored) × 1,500 (metric data points) = 3,000 included custom metric data points1 (hosts monitored) × 1,500 (metric data points) = 1,500 included custom metric data points1 (hosts monitored) × 1,500 (metric data points) = 1,500 included custom metric data pointsCustom metric data point consumption takes many forms. An equal number of custom metric data points can be consumed:
Dynatrace provides various options to help you understand and analyze your organization's consumption of Infrastructure Monitoring.
License managers can view usage and costs in Account Management.

Go to Account Management > Subscription > Overview > Cost and usage details > Usage summary.
Select the Infrastructure Monitoring capability.
From this screen, you can also drill down into usage detail on the capability and environment level.
For more information, see Overview (Dynatrace Platform Subscription).
builtin:billing.infrastructure_monitoring.metric_data_points.ingested_by_host metric to identify high-consuming hosts and correlate with their business value.You can use Dynatrace to automate some of your optimization efforts:
Notebooks and
Workflows.No. Host-hour consumption is independent of host memory size. Each monitored host contributes one host hour per hour of monitoring regardless of how much RAM it has. This is different from Full-Stack Monitoring, which scales with memory.
Both use host hours as the unit of measure, but Infrastructure Monitoring provides significantly deeper observability:
Data points beyond the 1,500 per host per 15-minute interval are billed as Custom Metrics Classic.
builtin:billing.infrastructure_monitoring.metric_data_points.included and builtin:billing.infrastructure_monitoring.metric_data_points.ingested to stay within budget.builtin:billing.infrastructure_monitoring.metric_data_points.ingested_by_host to identify which hosts are the source of the overage.Consumption is calculated in 15-minute intervals. If a host is monitored for fewer than 15 minutes in a given interval, its consumption is rounded up to 15 minutes. This ensures short-lived cloud instances are billed accurately.
OneAgent automatically ingests logs in all monitoring modes, including Infrastructure Monitoring. However, log ingestion doesn't consume Infrastructure Monitoring host hours; it is billed separately as Log Management and Analytics.
Yes. Dynatrace Extensions can be enabled on Infrastructure Monitoring hosts. Extensions may generate custom metric data points, which are counted against the 1,500 included data points per host per 15-minute interval. Any excess is billed separately.