For hardware and system requirements for other ActiveGate purposes, see:
For optimal performance and enhanced security, we recommend installing and running ActiveGate on a dedicated system. Utilizing ActiveGate on a dedicated system not only minimizes the risk of compromising ActiveGate authentication data but also reduces the potential for malicious configuration manipulation.
You need a machine dedicated to ActiveGate that has:
For large environments, you may need to use a machine with additional CPU and memory.
Space allocation per directory, for installation purposes:
(for more detailed allocation, refer to ActiveGate directories)
Top-level directory
Disk space requirements
ActiveGate and autoupdater executable files, libraries, and related files
%PROGRAMFILES%\dynatrace\gateway
relative to installation parameter: <INSTALL>\gateway
also configurable in GUI during installation
300 MB
ActiveGate configuration and related directories
For Environment ActiveGate, it also contains Extensions 1.0 and Extensions 2.0 configuration
%PROGRAMDATA%\dynatrace
2 MB
For Environment ActiveGate only: Extensions 1.0 and Extensions 2.0 executable files, libraries, and related files
%PROGRAMFILES%\dynatrace\remotepluginmodule
relative to installation parameter: <INSTALL>\remotepluginmodule
also configurable in GUI during installation
850 MB
Space allocation per directory, for ActiveGate operation:
(for more detailed allocation, refer to ActiveGate directories)
Top-level directory
Disk space requirements
ActiveGate and autoupdater logs
ActiveGate packages directory for auto-update installer downloads
%PROGRAMDATA%\dynatrace
1.2 GB
ActiveGate temporary files
%PROGRAMDATA%\dynatrace\gateway\tmp
4 GB (including 3 GB for cached OneAgent installers and container images)
Dump files uploaded to ActiveGate by OneAgent
%PROGRAMDATA%\dynatrace\gateway\dump
Functionality off by default. When activated, can take configurable maximum size: default 100 GB.
For Environment ActiveGate only: ActiveGate Extensions 1.0 and Extensions 2.0 logs, cache, run-time work area
%PROGRAMDATA%\dynatrace\remotepluginmodule
2 GB
For Environment ActiveGate only: ActiveGate extensions upload directory
%PROGRAMFILES%\dynatrace\remotepluginmodule\plugin_deployment
Depending on uploaded extensions
Extension Execution Controller logs retransmission persistence directory
%PROGRAMDATA%\dynatrace\remotepluginmodule\agent\runtime\extensions\persistence
Up to 600 MB by default. 1
The reliability mechanism does not work if the requirement is not met. Extra 1.5 GB required as a buffer. For more information see Persistence details.
The reliabilty mechanism ensures the persitance of Extension Execution Controller (EEC) logs in case ActiveGate or OneAgent is unavailable, there are network problems, or EEC experiences the data ingest overload. Thanks to the reliability mechanism, we're able to minimize the gaps in the log coverage.
Windows configuration file: C:\ProgramData\dynatrace\remotepluginmodule\agent\conf\extensionsuser.conf
Linux configuration file: /var/lib/dynatrace/remotepluginmodule/agent/conf/extensionsuser.conf
Variable
Description
persistence.reliable_mode
true - reliable mode turned on; SFM logs genereted if space requirement not met
false - reliable mode turned off; log ingest will be transmitted without the reliability mechanism
persistence.total_limit_kb
Maximum volume limit for Extensions Log Persistence in kilobytes. By default: 600 MB Can be modified manually if the requirement can't be met on the host.
NT AUTHORITY\LocalService account.The following table represents the machine instance size requirement based on number of OneAgents communicating with the ActiveGate. On each host, OneAgent is performing eight monitoring tasks:
The real number of hosts may be different depending on the monitored technologies in your environment. It is recommended that the machine on which ActiveGate is running should not exceed 50% CPU and 80% memory. Additionally, it must be assumed that ActiveGates may be inoperable during updates, restarts or short communication problems. In order to ensure high availability, operating ActiveGates should be able to takeover traffic of the unavailable ActiveGates
The C6i machine instances and the estimates:
Instance
vCPU
Mem (GiB)
Storage
Dedicated EBS bandwidth (Mbps)
Network performance
Estimated number of hosts
c6i.large
2
3.75
EBS-Only
500
Moderate
800
c6i.xlarge
4
7.5
EBS-Only
750
High
1800
c6i.2xlarge
8
15
EBS-Only
1,000
High
2500