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.
- 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
A freshly installed ActiveGate can run your private synthetic monitors (both HTTP and browser monitors) on the following operating systems.
|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.271 to 1.277||117|
|1.267 to 1.269||113|
|1.257 to 1.259||108|
|1.245 to 1.249||103|
|1.235 to 1.239||99|
|1.225 to 1.227||92|
|1.221 to 1.223||91|
|1.215 to 1.217||89|
|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.
Antivirus software on Windows
We do not support Synthetic-enabled ActiveGates on Windows hosts with antivirus software installed. The antivirus software might block the browser used to run the monitors.
|Red Hat Enterprise Linux||7.9, 8.4, 8.6, 8.7, 8.8, 9.0, 9.1, 9.2|
|Ubuntu||18.04, 20.04, 22.04|
|Amazon Linux 2|
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 and CentOS, 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:
Chromium development for Ubuntu 16.04 stopped at version 90.
Chromium development for Ubuntu 18.04 stopped at version 112.
|ActiveGate version||Latest supported Chromium version Red Hat, CentOS, Amazon Linux 2, Oracle Linux||Latest supported Chromium version Ubuntu|
|1.277||117 Red Hat/CentOS 7 and Amazon Linux 2, Red Hat/Oracle Linux 8, Red Hat 9||117 Ubuntu 18.041, Ubuntu 20.04 and 22.04|
|1.2752||117 Red Hat/CentOS 7 and Amazon Linux 2, Red Hat/Oracle Linux 8, Red Hat 9||1171 Ubuntu 18.04, Ubuntu 20.04 and 22.04|
|1.271 to 1.273||117 Red Hat/CentOS 7 and Amazon Linux 2, Red Hat 8||1171 Ubuntu 18.04, Ubuntu 20.04 and 22.04|
|1.269||113 Red Hat/CentOS 7 and Amazon Linux 2, Red Hat 8||113 Ubuntu 18.041, Ubuntu 20.04 and 22.04|
|1.267||1131 Red Hat/CentOS 7, Amazon Linux 2, Red Hat 8||113 Ubuntu 18.041, Ubuntu 20.04 and 22.04|
|1.265||111 Red Hat/CentOS 7 and Amazon Linux 2, 110 Red Hat 8||111 Ubuntu 18.04, Ubuntu 20.04 and 22.04|
|1.263||110 Red Hat/CentOS 7 and Amazon Linux 2, Red Hat 8||110 Ubuntu 18.04, Ubuntu 20.04 and 22.04|
|1.261||109 Red Hat/CentOS 7 and Amazon Linux 2, Red Hat 8||109 Ubuntu 18.04, Ubuntu 20.04 and 22.04|
|1.257 to 1.259||108 Red Hat/CentOS 7 and Amazon Linux 2, Red Hat 8||108 Ubuntu 18.04, Ubuntu 20.04 and 22.04|
|1.255||1071 Red Hat/CentOS 7, Amazon Linux 2, Red Hat 8||107 Ubuntu 18.04, Ubuntu 20.04 and 22.04|
|1.253||1061 Red Hat/CentOS 7, Amazon Linux 2, Red Hat 8||106 Ubuntu 18.041, Ubuntu 20.04 and 22.04|
|1.251||1051 Red Hat/CentOS 7, Amazon Linux 2, Red Hat 8||105 Ubuntu 18.04, Ubuntu 20.04 and 22.04|
|1.249||103 Red Hat/CentOS 7, Red Hat 8||103 Ubuntu 18.04, Ubuntu 20.04 and 22.04|
|1.245 to 1.247||103 Red Hat/CentOS 7, Red Hat 81||103 Ubuntu 18.04, Ubuntu 20.04 and 22.04|
|1.243||1011 Red Hat/CentOS 7, Red Hat 8||101 Ubuntu 18.04, 100 Ubuntu 20.04|
|1.241||1001 Red Hat/CentOS 7, Red Hat 8||100 Ubuntu 18.04, Ubuntu 20.04|
|1.235 to 1.239||99 Red Hat/CentOS 7, Red Hat 8||99 Ubuntu 18.04, Ubuntu 20.04|
|1.231 to 1.233||96 Red Hat 8||96 Ubuntu 18.041, Ubuntu 20.04|
|1.229||94 Red Hat 8||94 Ubuntu 18.04, Ubuntu 20.04|
|1.225 to 1.227||921||92 Ubuntu 20.04|
|1.221 to 1.223||911||91 Ubuntu 18.04, Ubuntu 20.04|
|1.219||90 Red Hat/CentOS 7, Red Hat 8||90 Ubuntu 16.04, Ubuntu 18.04, Ubuntu 20.04|
|1.215 to 1.217||89 Red Hat/CentOS 7, Red Hat 8||89 Ubuntu 16.04, Ubuntu 18.04, Ubuntu 20.04|
|1.213||88 Red Hat/CentOS 7, Red Hat 8||88 Ubuntu 20.04|
|1.209 to 1.211||87 Red Hat/CentOS 7, Red Hat 8||87 Ubuntu 16.04, Ubuntu 18.04|
|1.205 to 1.207||861||86 Ubuntu 16.04, Ubuntu 18.04|
|1.201 to 1.203||84||84|
Version not provided by Dynatrace. This means that the Chromium version is not available at the time of the ActiveGate release but will be provided by Dynatrace as soon as an official release of the version is available. Dynatrace includes the latest available version from the official distribution.
In such cases, Chromium can be autoupdated to the latest version provided by Dynatrace. The specified ActiveGate version will work with the latest supported Chromium version if installed outside of an autoupdate.
Introduced support for Red Hat 9.0 and Oracle Linux 8.8.
Based on the number of tests executed per hour, Synthetic-enabled ActiveGates need to meet the following hardware requirements.
|Minimum CPUs||2 vCPU||4 vCPU||8 vCPU||16 vCPU|
|Minimum free disk space||20 GB||25GB||30GB||40GB|
|Minimum free RAM||3GB||5GB||8GB||12GB|
|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|
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.
Calculated as 5000 monitor executions (maximum for a single environment) run once every minute (maximum frequency).
These are HTTP monitors on private locations with any of: pre- or post-execution scripts, OAuth2 authorization, Kerberos authentication.
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.