Ensure that the host you want to use for your private location complies with the following requirements.
There are no new versions of Chromium for Red Hat/Oracle Linux/Rocky Linux 8 beyond version 133. For important security and stability reasons, we've decided to discontinue our support for installing Synthetic-enabled ActiveGate on Red Hat/Oracle Linux/Rocky Linux 8 after ActiveGate version 1.325.
To ensure the continuity and security of your synthetic monitors, we recommend migrating your Synthetic-enabled ActiveGate to one of the supported operating systems, for example Red Hat/Oracle Linux/Rocky Linux 9.
We plan to have ActiveGate version 1.325 as the last Synthetic-enabled ActiveGate supported on Red Hat/Oracle Linux/Rocky Linux 8.
Additionally, with Dynatrace version 1.326, we plan to introduce mechanisms preventing Synthetic-enabled ActiveGates on Red Hat/Oracle Linux/Rocky Linux 8 from being updated beyond version 1.325.
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 the following directories and processes to the allowed list or excluding them from the policy:
Directories:
synthetic in their path. For an overview of directories in use, see ActiveGate directories.Processes:
This is the minimal list of processes and directories required for Dynatrace Synthetic to operate. It's not guaranteed that the service will function correctly with only these exclusions. 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 OS | Versions |
|---|---|
| Windows Server | 2016, 2019, 2022 |
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.319 | 138 |
| 1.317 | 137 |
| 1.315 | 136 |
| 1.313 | 135 |
| 1.311 | 134 |
| 1.309 | 133 |
| 1.307 | 132 |
| 1.305 | 130 |
| 1.303 | 129 |
| 1.299 to 1.301 | 128 |
| 1.295 to 1.297 | 126 |
| 1.293 | 125 |
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 distribution | Versions |
|---|---|
| Red Hat Enterprise Linux1 | 8.8, 8.10, 9.2, 9.4, 9.5 |
| Ubuntu | 20.04, 22.04, 24.04 |
| Amazon Linux | 2023 |
| Oracle Linux2 | 8.10, 9.5 |
| Rocky Linux3 | 8.10, 9.6 |
The Synthetic installer can be installed on all minor releases of Red Hat Enterprise Linux 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.
The Synthetic installer can be installed on all minor releases of Oracle Linux 8 and 9. However, we recommend using the latest currently supported versions according to documentation for Oracle Linux 8 and Oracle Linux 9.
The Synthetic installer can be installed on all minor releases of Rocky Linux 8 and 9. However, we recommend using the latest currently supported versions according to Rocky Linux Release and Version Guide.
ActiveGate version 1.305 is the last Synthetic-enabled ActiveGate to support Red Hat/CentOS 7.
ActiveGate version 1.307 is the last Synthetic-enabled ActiveGate to support Amazon Linux 2.
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 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.
Due to changes in libdav1d.so.6 packet availability Chromium versions older than 130 cannot be installed on Red Hat/Rocky Linux 9.
Please refer to troubleshooting guide for details.
Introduced support for Rocky Linux 8 and Rocky Linux 9.
Introduced support for Amazon Linux 2023.
Introduced support for Ubuntu 24.
Introduced support for Oracle Linux 9.
fapolicyd)If not configured correctly, the File Access Policy Daemon (fapolicyd) can potentially affect Dynatrace Synthetic monitoring capabilities. Similarly to antivirus or anti-malware software, fapolicyd might block the Chromium browser or Dynatrace processes responsible for executing synthetic monitors.
To ensure proper stability and performance, consider adding directories and processes to the allowed list or excluding them from the policy. For more detailed information, refer to the Red Hat documentation on fapolicyd. Prior to contacting Dynatrace support to troubleshoot issues with your private synthetic locations, make sure that fapolicyd was excluded as a source of problems.
File Access Policy Daemon framework can be run in debug mode where all denials are logged, making tracking down missing rules and troubleshooting issues easier. For more detailed information about its debug mode, refer to the documentation on troubleshooting problems related to fapolicyd
Based on the number of tests executed per hour, Synthetic-enabled ActiveGates need to meet the following hardware requirements.
The estimated limits listed in the table below were determined in our internal tests. The actual values might vary depending on the complexity of your monitors.
While XS nodes can be used on Windows Server-based ActiveGates, they may not be the best fit due to the higher hardware demands of Chromium. For optimal performance and to prepare for future enhancements, we recommend having at least 8 GB of RAM and 25 GB of free disk space.
On Linux systems with only 4 GB of RAM, the increasing resource requirements of Chrome (or Chromium), combined with the installation of third-party tools on the host, may lead to occasional memory shortages. Upgrading to 8 GB of RAM is strongly recommended to help ensure a smoother and more reliable experience.
| Node with browser monitor support | Browserless node | |
|---|---|---|
| Minimum CPUs | 2 vCPU | 1 vCPU |
| Minimum free disk space | 20 GB | 17 GB |
| Minimum RAM | 4 GB | 4 GB |
| Minimum free RAM | 3 GB | 2,7 GB |
| Minimum disk IOPS (Windows) | 100 | 100 |
| Estimated maximum number of HTTP monitor executions/h1 | 300k | 300k |
| Estimated maximum number of high-resource HTTP monitor2 executions/h | 10k | 10k |
| Estimated maximum number of browser monitor executions/h | 300 | - |
| Estimated maximum number of NAM ICMP monitor packets/h3 5 | 500k | 500k |
| Estimated maximum number of NAM TCP monitor requests/h4 6 | 1M | 1M |
| Estimated maximum number of NAM DNS monitor request/h4 7 | 100k | 100k |
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.
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.
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.
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.
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.
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)
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%\dynatrace600 MB
For executable files, libraries, and related files
<LOGS>
/var/log/dynatrace%PROGRAMDATA%\dynatrace1.7 GB
<CONFIG>
/var/lib/dynatrace%PROGRAMDATA%\dynatrace1 MB
<TEMP>
/var/tmp/dynatrace%PROGRAMDATA%\dynatrace21 GB1
For an XS ActiveGate—more space is required for execution logs on larger ActiveGates.
/tmpSynthetic-enabled ActiveGate requires write access to the /tmp directory during runtime. Its dependencies, including xvfb, utilize /tmp for storing temporary files and runtime data.
Lack of write permissions to this directory may result in unexpected failures or degraded functionality.
Ensure that the host environment provides sufficient access rights and available space in /tmp to support these operations reliably.