Review the hardware requirements before installing Dynatrace Managed. Exact sizing of a Managed Cluster is not always possible, especially in environments with growing traffic. While upfront analysis is useful, it's more important to be able to add capacity as your monitoring needs increase. Plan to scale along these dimensions:
A minimum 3-node cluster is required for production environments to ensure reliability and data redundancy. For details, see Multi-node installations.
The hardware requirements in the following tables are estimates based on typical environments and load patterns. Individual environments may vary. Column definitions:
Minimum node specifications — CPU and RAM must be exclusively available for Dynatrace. Disable CPU power-saving mode. CPUs must run at 2 GHz or faster; hosts must have at least 32 GB RAM.
Transaction Storage — distributed across all nodes, not stored redundantly. In multi-node clusters, the total transaction storage is divided by the number of nodes.
Long-term Metrics Store — in multi-node installations, three copies of the metrics store are saved. For four or more nodes, the per-node storage requirement decreases.
Keep the Long-term Metrics Store below 2 TB per node. Stability and operational resilience are ensured up to 4 TB per node. Persistent storage growth degrades cluster performance, resilience, and availability, and causes issues when adding nodes. If more storage is needed, add another node to reduce the per-node requirement.
| Node Type | Max host units1 monitored (per node) | Peak user actions/min (per node) | Min node specifications | Disk IOPS (per node) | Transaction Storage (10 days code visibility) | Long-term Metrics Store (per node) | Elasticsearch (per node) (35 days retention) |
|---|---|---|---|---|---|---|---|
Micro | 50 | 1000 | 4 vCPUs, | 500 | 50 GB | 100 GB | 50 GB |
Small | 300 | 10000 | 8 vCPUs, | 3000 | 300 GB | 500 GB | 500 GB |
Medium | 600 | 25000 | 16 vCPUs, | 5000 | 600 GB | 1 TB | 1.5 TB |
Large | 1250 | 50000 | 32 vCPUs, | 7500 | 1 TB | 2 TB | 1.5 TB |
XLarge3 | 2500 | 100000 | 64 vCPUs, | 10000 | 2 TB | 4 TB | 3 TB |
The size of a host for licensing purposes (based on the amount of RAM provided by a host). The size of a host (in other words, the number of host units that a host is comprised of for consumption calculations) is based on the number of GBs of RAM available on the host server. The advantage of this approach is its simplicity; technology-specific factors are not taken 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. For full details, see Application and Infrastructure Monitoring (Host Units).
See RAM requirements in Log Monitoring recommendations.
While Dynatrace Managed runs resiliently on instances with 1 TB+ RAM/128 cores (2XLarge) and allows you to monitor more entities, it's not the optimal way of utilizing the hardware. Instead, we recommend that you use smaller instances (Large or XLarge).
| Node Type | Max host units monitored (per node) | Peak user actions/min (per node) | Min node specifications | Disk IOPS (per node) | Transaction Storage (10 days code visibility) | Long-term Metrics Store (per node) | Elasticsearch (per node) (35 days retention) |
|---|---|---|---|---|---|---|---|
Large | 600 | 25000 | 32 vCPUs, | 7500 | 1 TB | 2 TB | 1.5 TB |
XLarge1 | 1250 | 50000 | 64 vCPUs, | 10000 | 2 TB | 4 TB | 3 TB |
While Dynatrace Managed runs resiliently on instances with 1 TB+ RAM/128 cores (2XLarge) and allows you to monitor more entities, it's not the optimal way of utilizing the hardware. Instead, we recommend that you use smaller instances (Large or XLarge).
To monitor 7,500 host units with a peak load of 300,000 user actions per minute in a Premium High Availability deployment, you need 6 XLarge nodes — 3 nodes in one data center and 3 in a second, each with 9 TB storage split across storage types.
Dynatrace Managed stores multiple types of monitoring data. Recommendations:
Disk size can vary depending on usage. For example, in a 2-node cluster where each node has 10 TB and transaction storage on both nodes is only 1.5 TB, a third node needs a minimum of 1 TB: (1.5 TB + 1.5 TB) / 3 = 1 TB. In a similar cluster where disks are 9 TB full, a third node needs a minimum of 6 TB: (9 TB + 9 TB) / 3 = 6 TB.
Anything below the calculated minimum is a misconfiguration. Note that multiple data sources — such as Session Replay — contribute to disk usage and can also trigger a misconfiguration.
Dynatrace Managed works with all common file systems. Use fast local storage suitable for database workloads. Dynatrace Managed also supports encrypted file systems, provided that disk IOPS meet the requirements and encryption is transparent at the operating system level (for example, Amazon EBS or Azure Storage encryption).
Requirements for Log Monitoring Classic:
Additional recommendations:
A minimum 3-node cluster is required for production environments to ensure reliability and data redundancy. All nodes in a multi-node cluster must: