Hardware and system requirements for routing/monitoring ActiveGates on Windows
Hardware and system requirements: Routing OneAgent traffic to Dynatrace, monitoring cloud environments, or monitoring remote technologies with extensions
For hardware and system requirements for other ActiveGate purposes, see:
- Hardware and system requirements for Synthetic-enabled ActiveGates, which support a subset of operating systems and are more demanding in terms of hardware and system requirements than are ActiveGates that are used for routing and monitoring.
- Hardware and system requirements for routing z/OS traffic to Dynatrace. ActiveGates running the zRemote module are more demanding in terms of hardware and system requirements than are ActiveGates that are used for routing and monitoring.
For optimal performance, we strongly recommend that you install and run the ActiveGate on a dedicated system.
Hardware requirements
You need a machine dedicated to ActiveGate that has:
- 4 GB free disk space for ActiveGate and Extensions installation, configuration, and logs for auto update purposes.
- 4 GB for ActiveGate and OneAgent cached installers and container images—if such will need to be stored.
- Space for dump files—if such will need to be stored. This functionality is turned off by default, but can be turned on in ActiveGate configuration. The maximum size of the storage space is configurable—100 GB by default.
- Space for extension uploads—depending on extensions used.
- 2 GB RAM (4 GB recommended).
- 1 dual core processor.
For large environments, you may need to use a machine with additional CPU and memory.
Space requirements per directory
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 | 300 MB |
ActiveGate configuration and related directories | 2 MB |
For Environment ActiveGate only: Extensions 1.0 and Extensions 2.0 executable files, libraries, and related files
| 350 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 | 1.2 GB |
ActiveGate temporary files | 4 GB (including 3 GB for cached OneAgent installers and container images) |
Dump files uploaded to ActiveGate by OneAgent | 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 | 2 GB |
For Environment ActiveGate only: ActiveGate extensions upload directory | Depending on uploaded extensions |
Supported operating systems
| Windows OS | Versions | CPU architectures |
|---|---|---|
| Windows | 8.1, 10 | x86-64 |
| Windows Server | 2012, 2012 R2, 2016, 2019 | x86-64 |
System requirements
- ActiveGate supports only operating systems running on the x86-64 architecture (64-bit Intel/AMD).
- Ensure that you have proper network port configuration.
- ActiveGate installation is not supported on Windows with a disabled
NT AUTHORITY\LocalServiceaccount.
AWS sizing guide
The following table represents the machine instance size requirement based on number of OneAgents communicating with the ActiveGate. On each host, OneAgent is performing seven monitoring tasks:
- Infrastructure monitoring
- Log monitoring
- Full-stack monitoring of 3 Apache Tomcat instances
- Full-stack monitoring of 2 Apache HTTP Server instances
| Machine size | Number of hosts |
|---|---|
| c4.large | 450 |
| c4.xlarge | 900 |
| c4.2xlarge | 1200 |
The C4 machine instances included in the estimates:
| Instance | vCPU | Mem (GiB) | Storage | Dedicated EBS bandwidth (Mbps) | Network performance |
|---|---|---|---|---|---|
| c4.large | 2 | 3.75 | EBS-Only | 500 | Moderate |
| c4.xlarge | 4 | 7.5 | EBS-Only | 750 | High |
| c4.2xlarge | 8 | 15 | EBS-Only | 1,000 | High |