Make sure the machine you'll use for your private location complies with the following requirements. Note that 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 on the following operating systems (both HTTP and browser monitors).
|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.197 to 1.199||83|
|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 on a non-production machine, for example your own desktop, you can install synthetic-enabled ActiveGates on unsupported Windows versions, such as Windows 10 or Windows Server 2012.
Antivirus software on Windows
We don't support synthetic-enabled ActiveGates on Windows machines that have antivirus software installed. The antivirus software may block the browser used to run the monitors.
|Red Hat Enterprise Linux||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 RHEL/CentOS||Latest supported Chromium version Ubuntu|
|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
Synthetic-enabled ActiveGates should meet the following hardware requirements depending on the number of tests executed per hour.
|Min CPUs||2 vCPU||4 vCPU||8 vCPU||16 vCPU|
|Min free disk||20 GB||25GB||30GB||40GB|
|Min free RAM||3GB||5GB||8GB||12GB|
|Estimated max number of browser monitor tests executed/h2||300||650||1200||2200|
|Max number of HTTP monitor tests executed/h2||300k||300k||300k||300k|
|Estimated max number of HTTP monitor tests with simple scripts executed/h2||10k||20k||60k||100k|
1 Not recommended for Windows Server-based ActiveGates. This is just a minimal requirement. We recommend at least 25GB of free disk space and 8GB RAM because of the enhancements planned for future releases.
2 As determined in our internal tests. The actual value may vary, depending on the complexity of your monitors. Calculated as 5000 tests (maximum for a single environment) run once every minute (maximum frequency).