Requirements for private Synthetic locations
Make sure the host you'll 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.
Operating system requirements
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 |
Chromium version on Windows
On Windows, the ActiveGate installer package includes the Chromium browser that's 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.225+ | 92 |
| 1.221+ | 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 |
| 1.197 to 1.199 | 83 |
| 1.195 | 80 |
| 1.189 to 1.193 | 79 |
| 1.183 to 1.187 | 78 |
| 1.173 to 1.181 | 74 |
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 Server 2012.
Antivirus software on Windows
We do not support Synthetic-enabled ActiveGates on Windows hosts that have antivirus software installed. The antivirus software might block the browser used to run the monitors.
Linux
| Linux distribution | Versions |
|---|---|
| Red Hat Enterprise Linux | 7.x, 8.x |
| Ubuntu | 16.04, 18.04, 20.04 |
| CentOS | 7.x, 8.x |
Chromium versions on Linux
On Linux, the ActiveGate installer downloads the Chromium dependencies that are required by the synthetic monitors engine. On Red Hat and CentOS, you'll 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.
| ActiveGate version | Latest supported Chromium version Red Hat/CentOS | Latest supported Chromium version Ubuntu |
|---|---|---|
| 1.225+ | 921 | 92 Ubuntu 20.04 |
| 1.221+ | 911 | 912 Ubuntu 16.04, Ubuntu 18.04, Ubuntu 20.04 |
| 1.219 | 90 Red Hat/CentOS 7, Red Hat/CentOS 8 | 90 Ubuntu 16.04, Ubuntu 18.04, Ubuntu 20.04 |
| 1.215 to 1.217 | 89 Red Hat/CentOS 7, Red Hat/CentOS 8 | 89 Ubuntu 16.04, Ubuntu 18.04, Ubuntu 20.04 |
| 1.213 | 88 Red Hat/CentOS 7, Red Hat/CentOS 8 | 88 Ubuntu 20.04 |
| 1.209 to 1.211 | 87 Red Hat/CentOS 7, Red Hat/CentOS 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 |
| 1.199 | 831 | 831 |
| 1.197 | 81 | 81 |
| 1.195 | 79 | 80 |
| 1.189 to 1.193 | 79 | 79 |
| 1.183 to 1.187 | 78 | 78 |
| 1.169 to 1.181 | 73 | 73 |
| 1
Version not provided by Dynatrace. | ||
| 2
Chromium development for Ubuntu 16.04 stopped at version 90. |
Hardware requirements
Depending 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 | 25GB | 30GB | 40GB |
| Minimum RAM | 4GB | 8GB | 16GB | 32GB |
| Minimum free RAM | 3GB | 5GB | 8GB | 12GB |
| 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 |
| 1
Not recommended for Windows Server-based ActiveGates. 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. |
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.