This topic explains the hardware and operating system requirements for installing Dynatrace Managed.
It's not always possible to provision nodes that are sized exactly right, particularly if your environment is subject to ever-increasing traffic levels. While it's useful to do upfront analysis of required size, it's more important to have the ability to add more capacity to your Dynatrace Managed cluster should your monitoring needs increase in the future. To leverage the full benefits of the Dynatrace Managed architecture, be prepared to scale along the following dimensions:
- Horizontally by adding more nodes
- Vertically by provisioning more RAM/CPU per node
- In terms of data storage, by being able to resize the disk volumes as required (for guidelines regarding recommended disk setup see below).
Dynatrace Managed stores multiple types of monitoring data, depending on the use case. We recommend:
- Storing Dynatrace binaries and the data store on separate mount points to allow the data store to be resized independently.
- Not keeping Dynatrace data storage on the root volume to avoid additional complexity when resizing the disk later, if required.
- Mounting different types of data storage on separate disk volumes for maximum flexibility and performance.
- Creating resizable disk partitions (for example, by leveraging Logical Volume Manager [LVM]).
The hardware requirements included in the following table are estimates based on typical environments and load patterns. Requirements for individual environments may vary.
|Node type||Max hosts monitored (per node)||Max user actions/s (per node)||Minimum node spec1||Disk IOPS (per node)||Transaction Storage2 (for 10 days code visibility)||Long-term Metrics Store3 (per node)||Elasticsearch (per node and for 35 days retention)|
|Trial||20||20||4 vCPUs, 16GB RAM||30||250GB||100GB||70GB|
|Small||250||250||8 vCPUs, 32GB RAM||150||500GB||1.2TB||700GB|
|Medium||600||500||16 vCPUs, 64GB RAM||300||1TB||2.5TB||2TB|
|Large||1500||1000||32 vCPUs, 128GB RAM||750||2TB||5TB||4TB|
|XLarge||3000||3000||64 vCPUs, 256GB RAM||1500||4TB||10TB||8TB|
1 CPU and RAM must be exclusively available for Dynatrace. Power saving mode for CPUs must be disabled. CPUs must run with a clock speed of at least 2GHz.
2 Transaction data is distributed across all nodes and is not stored redundantly. So for multi-node clusters, the storage per node is divided by the number of nodes.
3 For multi-node installations we keep three copies of the metrics store. For 4 or more nodes the storage requirement per node is reduced.
Also see the directory structure of Dynatrace Managed.
To monitor 8k hosts with a peak load of 3k user actions per second, you need 3 extra large nodes with a combined storage of 4TB for direct storage and 30TB for long-term metrics.
To monitor 200 hosts with a peak load of 500 user actions per second, you need 1 medium node with storage of 1TB for transactions and 2.5TB for long-term metrics,or to have failover you can also use 3 small nodes.
We recommend multi-node setups for failover and data redundancy. A sufficiently sized 3-node cluster is the recommended setup. For Dynatrace Managed installations with more than one node, all nodes must:
- Use the same Linux distribution
- Have the same hardware configuration
- Be synchronized with NTP
- Be in the same time zone
- Be able to communicate over a private network on multiple ports
You'll need a dedicated host for Dynatrace Managed installation. This host must not run other services that are CPU or memory intensive, or that open ports used by Dynatrace Managed.
Dynatrace Server requires a fixed IP assignment.
Ensure that you've appropriately configured your firewall settings
The libraries that are installed with Dynatrace Managed are locale-aware. For correct display of text and symbols, be sure to set your environment's system locale to an English language option (for example,
For details on which 64-bit Linux distributions you can install Dynatrace Managed on, please see operating system requirements for Managed Server. Note that installation on both physical and virtualized hosts is supported, but installation in containers isn't supported.
Please also check the requirements regarding ActiveGate