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.

Run ActiveGate on dedicated system

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.

Refer to the Log Management and Analytics default limits doc page for detailed log throughput characteristics on Environmental Active Gate for logs ingest API.

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.
2 GB free disk space for Extension Execution Controller logs retransmission persistence file.
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
default: /opt/dynatrace
relative to installation parameter: <INSTALL>

300 MB

ActiveGate configuration and related directories
For Environment ActiveGate, it also contains Extensions 1.0 and Extensions 2.0 configuration
default: /var/lib/dynatrace
relative to installation parameter: <CONFIG>

2 MB

For Environment ActiveGate only: Extensions 1.0 and Extensions 2.0 executable files, libraries, and related files default: /opt/dynatrace/remotepluginmodule
relative to installation parameter: <INSTALL>/remotepluginmodule

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
default: /var/log/dynatrace
installation parameter: <LOG>

700 MB

ActiveGate packages directory for auto-update installer downloads
default: /var/lib/dynatrace/packages
installation parameter: <PACKAGES_DIR>

500 MB

ActiveGate temporary files
default: /var/tmp/dynatrace/gateway
path relative to installation parameter TEMP: <TEMP>/gateway

4 GB (including 3 GB for cached OneAgent installers and container images)

Dump files uploaded to ActiveGate by OneAgent
/var/lib/dynatrace/gateway/dump

Functionality off by default, not configurable at installation time.
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
default: /var/lib/dynatrace/remotepluginmodule
path relative to installation parameter CONFIG: <CONFIG>/remotepluginmodule

2 GB

For Environment ActiveGate only: ActiveGate extensions upload directory
default: /opt/dynatrace/remotepluginmodule/plugin_deployment
path relative to installation parameter INSTALL: <INSTALL>/remotepluginmodule/plugin_deployment

Depending on uploaded extensions

Extension Execution Controller logs retransmission persistence file default: /var/lib/dynatrace/remotepluginmodule/agent/runtime
path relative to installation parameter INSTALL: <INSTALL>/remotepluginmodule/agent/runtime

Up to 2 GB by default. Depending on volume of logs ingest.

Supported operating systems

Linux distribution

Versions

CPU architectures

Amazon Linux

2¹, 2023²

ARM64 (AArch64), x86-64

CentOS

7.9

x86-64

Oracle Linux

7.9, 8.10, 9.4

x86-64

Oracle Linux

8.10, 9.4

ARM64 (AArch64)

Red Hat Enterprise Linux

7.9, 8.8, 8.10, 9.2, 9.4

s390, x86-64

Red Hat Enterprise Linux

8.10, 9.4

ARM64 (AArch64)

Rocky Linux

8.10, 9.4

ARM64 (AArch64), x86-64

SUSE Enterprise Linux

15.5, 15.6

s390, x86-64

SUSE Enterprise Linux

15.6

ARM64 (AArch64)

Ubuntu

16.04, 18.04, 20.04, 22.04, 24.04

x86-64

Ubuntu

20.04, 22.04, 24.04

ARM64 (AArch64), s390

Not supported for the zRemote module

Not supported for the zRemote module. To run ActiveGate extensions, the ActiveGate needs the "libcrypt.so.1" library from the "libxcrypt-compat.rpm" package, which is not installed by default on Amazon Linux 2023.

ActiveGate installed on the x86-64 architecture supports all functionalities. Other architectures provide only partial support. 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 eight monitoring tasks:

Infrastructure monitoring
Log monitoring
Full-stack monitoring of 3 Apache Tomcat instances
Full-stack monitoring of 2 Apache HTTP Server instances
Extension monitoring

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

x86-64 architecture

The C6i machine instances and the estimates:

Instance

vCPU

Mem (GiB)

Storage

Dedicated EBS bandwidth (Mbps)

Network performance

Estimated number of hosts

c6i.large

3.75

EBS-Only

500

Moderate

800

c6i.xlarge

7.5

EBS-Only

750

High

1800

c6i.2xlarge

EBS-Only

1,000

High

2500

ARM64 (AArch64) architecture

The C7g machine instances and the estimates:

Instance

vCPU

Mem (GiB)

Storage

Dedicated EBS bandwidth (Mbps)

Network performance

Estimated number of hosts

c7g.large

3.75

EBS-Only

500

Moderate

1300

c7g.xlarge

7.5

EBS-Only

750

High

2700

c7g.2xlarge

EBS-Only

1,000

High

5500

s390 architecture

Machine sizes and estimates:

Machine size

CPU

Mem (GiB)

Estimated number of hosts

800

1500