Hardware and system requirements for routing/monitoring ActiveGates on Linux
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 ActiveGates that are used for routing and monitoring.
- Hardware and system requirements for the zRemote module for z/OS monitoring. 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 purposes.
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
default: | 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 | 700 MB |
ActiveGate packages directory for auto-update installer downloads | 500 MB |
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, not configurable at installation time. |
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
Linux distribution | Versions | CPU architectures |
---|---|---|
Amazon Linux 2 | All versions supported | x86-64 |
Amazon Linux AMI | 2018.3 | x86-64 |
CentOS | 7.9 | x86-64 |
Oracle Linux | 7.9, 8.4 | x86-64 |
Red Hat Enterprise Linux | 7.9, 8.4, 8.6, 9.0 | s390, x86-64 |
SUSE Enterprise Linux | 15.1, 15.2, 15.3 | x86-64 |
15.3 | s390 | |
Ubuntu | 16.04, 18.04, 20.04, 22.04 | x86-64 |
20.04 | s390 |
Note: ActiveGate installed on the s390 architecture supports OneAgent routing and monitoring, and mainframe monitoring. Extensions and private Synthetic locations are not supported. For details, see ActiveGate purposes and functionality.
System requirements
-
Ensure that you have proper network port configuration.
-
Your operating system must handle at least 500,000 open files for the
dtuserag
user.
To view the system limit, execute the following command:[user@host]# cat /proc/sys/fs/file-max
Also, it may be that you've checked out too many open files in Linux.
-
Your operating system must have at least 20,000 processes available to the
dtuserag
user.
To view the system limit, execute the following command:[user@host]# cat /proc/sys/kernel/pid_max
-
The ActiveGate Linux installer doesn't support ACL (Access Control List). ACL rules may prohibit access to installer-created directories and files, making the ActiveGate fail to start. If you use the ACL, rules related to the installation directories defined in the following parameters should be disabled:
INSTALL= CONFIG= LOG= TEMP= PACKAGES_DIR=
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
x86-64 architecture
The C4 machine instances and the estimates:
Instance | vCPU | Mem (GiB) | Storage | Dedicated EBS bandwidth (Mbps) | Network performance | Estimated number of hosts |
---|---|---|---|---|---|---|
c4.large | 2 | 3.75 | EBS-Only | 500 | Moderate | 450 |
c4.xlarge | 4 | 7.5 | EBS-Only | 750 | High | 900 |
c4.2xlarge | 8 | 15 | EBS-Only | 1,000 | High | 1200 |
s390 architecture
Machine sizes and estimates:
Machine size | CPU | Mem (GiB) | Estimated number of hosts |
---|---|---|---|
S | 2 | 4 | 800 |
M | 4 | 8 | 1500 |