Allocate host unit quotas
You can split your licensed quota of host units across environments based on your needs. For example, you might want to allocate most of your host units to your production monitoring environment and allocate the remaining host units to your pre-production environment.
Allocating host-unit quotas across environments is possible for both Dynatrace SaaS and Managed deployments.
In the user menu in the upper-right corner, go to Account settings.
On the License details settings page, look for the Consumption by environment section. This section appears if:
- You have more than one Dynatrace environment.
- Your license doesn’t permit overages (or your license does permit overages, but they’re limited to a certain amount).
Note that the example license below stipulates that no overages are allowed (when a license does allow overages, setting quotas for individual environments doesn’t make sense as these limits can be exceeded).
- To view and set host unit quotas, go to Environment management > Quotas and overage.
Dynatrace provides a default allocation of host units based on your license. If you decide to set limits for each environment, Dynatrace shows you the remaining number of available host units. For example, suppose you have two environments and the total number of host units is 13. If you allocated six units to the first environment and you select three for the second environment, Dynatrace will inform you that there are still four host units left to distribute.
If your license allows overages, but the overages are capped, you’ll see an Allow overages option box for each environment. Select this setting to allow authorized users to enable overages for mission-critical environments and production servers that have high load.
When host unit limits are reached
When the configured limit for concurrent host units for an environment is reached–assuming that the account is not entitled to use overages—Dynatrace begins enforcing the available limit.
Enforcing a limit on concurrent host units means that Dynatrace decides which hosts to continue monitoring and for which hosts monitoring will be stopped. The decision is based on the start times of the OneAgents installed on the monitored hosts. When the limit is reached, Dynatrace disables monitoring on the most recently started OneAgents that exceed the concurrent host unit limit.
Example: Let’s assume a configured limit of six concurrent host units for each environment, and the following hosts with installed OneAgents:
|Monitored host||OneAgent start time||Size (GB)||Host units||Concurrent host units|
|Host 1||2022-Jan-04 01:12am||32 GB||2||2|
|Host 2||2022-Jan-04 02:43am||48 GB||3||5|
|Host 3||2022-Jan-04 11:18pm||16 GB||1||6|
|Host 4||2022-Jan-05 10:12am||32 GB||2||8 (monitoring disabled)|
|Host 5||2022-Jan-05 10:13am||16 GB||1||9 (monitoring disabled)|
When the OneAgents on Host 4 and Host 5 start reporting data, the configured limit of 6 concurrent host units is exceeded. At that point, Dynatrace disables monitoring of these two hosts and continues monitoring Hosts 1-3.