Requirements for private Synthetic locations

Ensure that the host you want to use for your private location complies with the following requirements. Note that a Synthetic-enabled ActiveGate has more demanding hardware and system requirements than a regular Environment or Cluster ActiveGate. Dynatrace strongly recommends using a Synthetic-enabled ActiveGate exclusively for synthetic monitoring purposes.

End-of-support information
  • Chromium development for Red Hat/CentOS 7 stopped at version 126. For important security and stability reasons, we've decided to discontinue our support for installing Synthetic-enabled ActiveGate on Red Hat/CentOS 7 after ActiveGate version 1.305. ActiveGate version 1.305 will be the last Synthetic-enabled ActiveGate supported on Red Hat/CentOS 7. Additionally, with Dynatrace version 1.306, we will introduce mechanisms preventing Synthetic-enabled ActiveGates on Red Hat/CentOS 7 from being updated beyond version 1.305.
    • Since RHEL7 reached End of Maintenance support on June 30th 2024, all it's packages have been archived. This means that it may not be possible to find the required dependencies for update.
  • Chromium development for Ubuntu 18.04 stopped at version 112. For important security and performance reasons, we’ve decided to discontinue our support for installing Synthetic-enabled ActiveGate on Ubuntu 18 after ActiveGate version 1.283. ActiveGate version 1.283 is the last Synthetic-enabled ActiveGate supported on Ubuntu 18. Additionally, with Dynatrace version 1.284, we have introduced mechanisms preventing Synthetic-enabled ActiveGates on Ubuntu 18 from being updated beyond version 1.283.
  • As Chromium development for Ubuntu 16.04 stopped at version 90, we can no longer assure a high enough level of stability and security for synthetic monitor execution on Ubuntu 16. We have discontinued our support for installing Synthetic-enabled ActiveGate on Ubuntu 16 after ActiveGate version 1.251. That is, ActiveGate version 1.251 is the last Synthetic-enabled ActiveGate supported on Ubuntu 16. With Dynatrace version 1.254, Synthetic-enabled ActiveGates on Ubuntu 16 can no longer be updated.
  • Check the latest ActiveGate release notes for the oldest supported ActiveGate versions.

Operating system requirements

Antivirus and Anti-Malware software

Antivirus and anti-malware software can adversely affect Dynatrace Synthetic monitoring capabilities. The antivirus or anti-malware software might block the Chromium browser or Dynatrace processes responsible for executing synthetic monitors, cause Synthetic-enabled ActiveGate installation failures, interfere with network communication, and impact the reliability of measurements.

To ensure proper stability and performance, consider adding directories and processes to the allowed list or excluding them from the policy. Collaborate with your vendor to appropriately allow expected behaviors from Dynatrace.

Prior to contacting Dynatrace support to troubleshoot issues with your private synthetic locations make sure that antivirus or anti-malware software was excluded as a source of problems.

A freshly installed ActiveGate can run your private synthetic monitors (both HTTP and browser monitors) on the following operating systems.

Windows

Windows OS
Versions
Windows Server
2016, 2019, 2022

Chromium version on Windows

On Windows, the ActiveGate installer package includes the Chromium browser used to run browser monitors. The table below shows the Chromium versions that are bundled with the respective ActiveGate versions.

ActiveGate version
Included Chromium version
1.299
127
1.295 to 1.297
126
1.289 to 1.293
125
1.287
122
1.285
121
1.283
120
1.281
119
1.279
118
1.271 to 1.277
117
1.267 to 1.269
113
1.265
111
1.263
110
1.261
109
1.257 to 1.259
108
1.255
107
1.253
106
1.251
105
1.245 to 1.249
103
1.243
101
1.241
100
1.235 to 1.239
99
1.231
96
1.229
95
1.225 to 1.227
92
1.221 to 1.223
91
1.219
90
1.215 to 1.217
89
1.213
88
1.209 to 1.211
87
1.205 to 1.207
86
1.201 to 1.203
84

Unsupported Windows versions for testing purposes only

If you only want to test private Synthetic locations on a non-production host, for example, your own desktop, you can install a Synthetic-enabled ActiveGate on unsupported Windows versions such as Windows 10 or Windows 11.

As of ActiveGate version 1.263+, Synthetic-enabled ActiveGate no longer works on Windows Server 2012 for testing purposes. Google has dropped support for Windows 2012 Server with Chromium 110, which is bundled with the ActiveGate version 1.263 installation package.

Linux

Linux distribution
Versions
Red Hat Enterprise Linux1
7.9, 8.4, 8.6, 8.8, 8.10, 9.0, 9.2, 9.4
Ubuntu
18.04, 20.04, 22.04
CentOS
7.9
Amazon Linux 2
Oracle Linux
8.8
Rocky Linux
8.9, 9.4
1

The Synthetic installer can be installed on all minor releases of Red Hat Enterprise Linux 7, 8, and 9. However, we recommend using the versions listed in this table, as they have Extended Life-cycle Support (ELS) according to Red Hat Enterprise Linux Life Cycle.

Chromium versions on Linux

We strongly recommend that you keep your Linux-based Synthetic-enabled ActiveGates and Chromium versions updated—Dynatrace supports Chromium versions that are no more than two versions behind the latest Dynatrace-supported version for a specific ActiveGate release. For example, if the latest supported Chromium version is 103, Dynatrace supports up to Chromium version 101. If the provided Chromium version is significantly older for a specific OS, we support only the provided version. See information on updating Chromium automatically and manually.

On Linux, the ActiveGate installer downloads the Chromium dependencies that are required by the Synthetic engine. On Red Hat, CentOS and Rocky, you need to enable particular repositories from which the installer downloads the dependencies. The Dynatrace web UI provides you with all the required commands. For detailed instructions, see Create a private synthetic location.

When installing ActiveGate and Chromium from a custom, local repository, you need to resolve all dependencies and enable repositories as required; the custom repository can be used only for Chromium packages, not their dependencies. Place the Chromium package archive and the signature file in the custom repository for installation. If your package archive file is https://synthetic-packages.s3.amazonaws.com/Chromium/snap/chromium-107.0.5304.87-2168.tgz (Chromium 107 for Ubuntu 20 and 22 on ActiveGate version 1.255), you can find the signature file by appending .sig to the URL: https://synthetic-packages.s3.amazonaws.com/Chromium/snap/chromium-107.0.5304.87-2168.tgz.sig.

  • Chromium development for Ubuntu 16.04 stopped at version 90.
  • Chromium development for Ubuntu 18.04 stopped at version 112.
  • Chromium development for Red Hat/CentOS 7 and Amazon Linux 2 stopped at version 126.
    • Since RHEL7 reached End of Maintenance support on June 30th 2024, all it's packages have been archived. This means that it may not be possible to find the required dependencies for update.
ActiveGate version
Latest supported Chromium version Red Hat, CentOS, Amazon Linux 2, Oracle Linux
Latest supported Chromium version Ubuntu
1.271 to 1.273
1171 Ubuntu 18.04, Ubuntu 20.04 and 22.04
1.267
1131 Red Hat/CentOS 7, Amazon Linux 2, Red Hat 8
1.255
1071 Red Hat/CentOS 7, Amazon Linux 2, Red Hat 8
1.253
1061 Red Hat/CentOS 7, Amazon Linux 2, Red Hat 8
1.251
1051 Red Hat/CentOS 7, Amazon Linux 2, Red Hat 8
1.243
1011 Red Hat/CentOS 7, Red Hat 8
1.241
1001 Red Hat/CentOS 7, Red Hat 8
1.231 to 1.233
96 Ubuntu 18.041, Ubuntu 20.04
1.225 to 1.227
921
1.201 to 1.203
1
2

Introduced support for Red Hat 9.0 and Oracle Linux 8.8.

3

Introduced support for Rocky Linux 8 and Rocky Linux 9.

Hardware requirements

Based on the number of tests executed per hour, Synthetic-enabled ActiveGates need to meet the following hardware requirements.

XS1
S
M
L
Minimum CPUs
2 vCPU
4 vCPU
8 vCPU
16 vCPU
Minimum free disk space
20 GB
25 GB
30 GB
40 GB
Minimum RAM
4 GB
8 GB
16 GB
32 GB
Minimum free RAM
3 GB
5 GB
8 GB
12 GB
Minimum disk IOPS (Windows)
100
200
400
750
Estimated maximum number of HTTP monitor executions/h2
300k
300k
300k
300k
Estimated maximum number of high-resource HTTP monitor3 executions/h
10k
20k
60k
100k
Estimated maximum number of browser monitor executions/h
300
650
1200
2200
Estimated maximum number of NAM ICMP monitor packets/h4 6
500k
1M
1.5M
2M
Estimated maximum number of NAM TCP monitor requests/h5 7
1M
2M
3M
4M
Estimated maximum number of NAM DNS monitor request/h5 8
100k
200k
300k
400k
1

Not recommended for Windows Server-based ActiveGates because of increased hardware requirements for Chromium.

This is just a minimal requirement. We recommend at least 25 GB of free disk space and 8 GB RAM because of the enhancements planned for future releases.

2

Calculated as 5000 monitor executions (maximum for a single environment) run once every minute (maximum frequency).

3

These are HTTP monitors on private locations with any of: pre- or post-execution scripts, OAuth2 authorization, Kerberos authentication.

4

For NAM monitors using ICMP request type, capacity is related to number of ICMP echo requests (packets) that are being sent during monitors execution. As this number of packets-to-be-sent may significantly vary among defined monitors, using the number of monitor executions as a capacity limit would be inaccurate.

5

For NAM monitors using TCP and DNS request types, capacity is related to the number of network connections (requests) that are being sent during monitors execution. As this number of requests may significantly vary among defined monitors, using the number of monitor executions as a capacity limit would be inaccurate.

6

During load tests that helped to establish capacity limits, NAM ICMP monitors were exclusively scheduled on location; monitors had the following characteristic. Actual capacity may be different for other environments (for example, those where monitored targets respond slower or are failing to provide a response within timeout limit or other type of monitors are executed at the same time).

Monitors were using default settings (including default timeouts settings and single packet per-request) and were scheduled every 1 minute.

There were multiple target hosts used during tests; all of them were responding properly with average RTT around 200ms.

7

During load tests that helped to establish capacity limits, NAM TCP monitors were exclusively scheduled on location; monitors had the following characteristic. Actual capacity may be different for other environments (for example, those where monitored targets respond slower or are failing to provide a response within timeout limit or other type of monitors are executed at the same time).

Monitors were using default settings (including default timeouts settings) and were scheduled every 1 minute.

There were multiple target hosts and ports used during tests; all of them were responding properly with average TCP connection time around 200ms.

8

During load tests that helped to establish capacity limits, NAM DNS monitors were exclusively scheduled on location; monitors had the following characteristic. Actual capacity may be different for other environments (for example, those where monitored targets respond slower or are failing to provide a response within timeout limit or other type of monitors are executed at the same time). Please note that DNS server used during resolution should be able to handle incoming requests and may not consider the incoming traffic as a subject to throttling or rejection (for example, due to detection as bot-originated).

Monitors were using default settings (including default timeouts settings and UDP as a transport) and were scheduled every 1 minute.

There were multiple resolution targets used during tests; all of them were resolved properly with average DNS resolution time around 10ms.

Publicly available DNS servers were used: Google (8.8.8.8 and 8.8.4.4) and Cloudflare (1.1.1.1 and 1.1.1.2)

Limit values

The estimated limits listed in the table above were determined in our internal tests. The actual values might vary depending on the complexity of your monitors.

You need to uninstall and reinstall your Synthetic-enabled ActiveGate to change its size, for example, after increasing the resources of your S-sized ActiveGate to meet the requirements for a size M. Reinstallation is required before you can make use of the updated resources for synthetic monitoring; otherwise, your ActiveGate will continue to show up as size S (Synthetic Node size) in Deployment Status and will be subject to the execution limits of size S.

The table below shows the default installation locations (Linux and Windows) of various ActiveGate directories and the minimum size requirements. This information is compiled from details in ActiveGate directories.

Installation parameter

Default path

Min. size

Notes

<INSTALL>

  • /opt/dynatrace/
  • %PROGRAMFILES%\dynatrace

600 MB

For executable files, libraries, and related files

  • 300 MB for ActiveGate
  • 270 MB for Private Synthetic files

<LOGS>

  • /var/log/dynatrace
  • %PROGRAMDATA%\dynatrace

1.7 GB

  • 500 MB for ActiveGate logs
  • 1 GB for Private Synthetic logs
  • 200 MB for autoupdater logs

<CONFIG>

  • /var/lib/dynatrace
  • %PROGRAMDATA%\dynatrace

1 MB

<TEMP>

  • /var/tmp/dynatrace
  • %PROGRAMDATA%\dynatrace

21 GB1

  • 1 GB for ActiveGate temporary files (without cached OneAgent installers and container images)
  • 20 GB for Private Synthetic temporary files (including execution logs, cache, and screenshots)
1

For an XS ActiveGate—more space is required for execution logs on larger ActiveGates.