If the web UI–guided installation fails or you prefer to prepare the host for the Synthetic engine yourself, you can install Chromium and other dependencies manually or from a custom repository.
This section is not relevant for browserless locations.
Amazon Linux 2023, Ubuntu and Oracle Linux 9 use Chrome for Testing instead of Chromium. For manual installation of Chrome for Testing on these operating systems, see Amazon Linux 2023, Ubuntu and Oracle Linux 9 (Chrome for Testing).
Ensure that you can connect to https://synthetic-packages.s3.amazonaws.com to access the browser packages. For security reasons, public access to the S3 bucket is enabled only for specific files; trying anything else will result in a 403 error.
Also see Install the browser from a custom repository below.
See how to update the browser manually in Manage private Synthetic locations. We strongly recommend that you keep your Linux-based Synthetic-enabled ActiveGates and browser versions updated—Dynatrace supports browser versions that are no more than two versions behind the latest Dynatrace-supported version for a specific ActiveGate release.
This section is only relevant for releases 1.329 and earlier.
Install Synthetic engine dependencies:
Synthetic engine dependencies:
sudo apt-get update && sudo apt-get -y install xvfb x11-xkb-utils xfonts-100dpi xfonts-75dpi xfonts-scalable libnss3-tools auditd
Chromium dependencies:
sudo apt-get -y install fonts-dejavu-core
sudo snap install gnome-3-38-2004 gtk-common-themes
Download and install Chromium.
Download the snap (Ubuntu Server 20.04 and 22.04) package archive. This is a safe and verified archive hosted by Dynatrace.
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/snap/chromium-142.0.7444.175-3313.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/snap/chromium-141.0.7390.122-3285.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/snap/chromium-140.0.7339.185-3251.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/snap/chromium-139.0.7258.138-3235.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/snap/chromium-138.0.7204.157-3203.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/snap/chromium-138.0.7204.100-3199.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/snap/chromium-137.0.7151.103-3169.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/snap/chromium-136.0.7103.59-3121.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/snap/chromium-135.0.7049.95-3110.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/snap/chromium-134.0.6998.35-3060.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/snap/chromium-132.0.6834.159-3036.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/snap/chromium-131.0.6778.85-3002.tgz
You can verify the authenticity of the packages using the signature files stored together with the package archives.
Extract the installation packages. Go to the directory where you saved the archive and run the following command:
mkdir /tmp/chromium ; tar xzf chromium.tgz -C /tmp/chromium
This creates a /tmp/chromium directory and extracts the packages into it.
Install the extracted packages.
sudo chown -R root:root /tmp/snap-private-tmp
sudo snap ack /tmp/chromium/chromium.assert
sudo snap install --devmode /tmp/chromium/chromium.snap
Substitute dtuserag with the names of the ActiveGate service user and group if they differ from the default values.
sudo chown -R dtuserag:dtuserag /tmp/snap-private-tmp
This installs all the packages extracted to the /tmp/chromium/ directory. You can delete the /tmp/chromium/ directory and the downloaded chromium.tgz archive after successful Chromium installation.
After you satisfy the dependencies, run the ActiveGate installer with root rights with the --enable-synthetic parameter set to manual. For example:
/bin/bash ./Dynatrace-ActiveGate-Linux.sh --enable-synthetic=manual
You can verify the authenticity of the packages using the signature files stored together with the package archives.
curl to use the correct proxy. Specify your proxy and port details by running the commands as in this example:
vi /root/.curlrcproxy=http://proxy.example.com:8080
Set up repositories and install dependencies.
ActiveGate version 1.305 is the last Synthetic-enabled ActiveGate to support Red Hat 7.
sudo subscription-manager register --auto-attach
Extras and Optional repositories as well as EPEL (Extra Packages for Enterprise Linux).
sudo subscription-manager repos --enable rhel-7-server-extras-rpmssudo subscription-manager repos --enable rhel-7-server-optional-rpmssudo rpm -Uvh https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
sudo yum install -y xorg-x11-server-Xvfb xorg-x11-xkb-utils xorg-x11-server-utils xorg-x11-fonts-100dpi xorg-x11-fonts-75dpi xorg-x11-fonts-Type1 libwayland-server mesa-libgbm curl nss-tools
Download and install Chromium.
Download the rpm package archive. This is a safe and verified archive hosted by Dynatrace.
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/rpm/chromium-143.0.7499.192-1.el9.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/rpm/chromium-142.0.7444.175-2.el9.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/rpm/chromium-141.0.7390.122-1.el9.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/rpm/chromium-133.0.6943.141-1.el8.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/rpm/chromium-140.0.7339.185-1.el9.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/rpm/chromium-133.0.6943.141-1.el8.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/rpm/chromium-139.0.7258.138-1.el9.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/rpm/chromium-133.0.6943.141-1.el8.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/rpm/chromium-138.0.7204.157-1.el9.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/rpm/chromium-133.0.6943.141-1.el8.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/rpm/chromium-138.0.7204.100-1.el9.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/rpm/chromium-133.0.6943.141-1.el8.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/rpm/chromium-137.0.7151.103-1.el9.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/rpm/chromium-133.0.6943.141-1.el8.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/rpm/chromium-136.0.7103.59-1.el9.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/rpm/chromium-133.0.6943.141-1.el8.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/rpm/chromium-135.0.7049.95-1.el9.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/rpm/chromium-133.0.6943.141-1.el8.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/rpm/chromium-134.0.6998.35-1.el9.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/rpm/chromium-132.0.6834.159-1.el8.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/rpm/chromium-132.0.6834.159-1.el9.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/rpm/chromium-126.0.6478.114-1.el7.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/rpm/chromium-131.0.6778.204-1.el8.tgz
curl --output chromium.tgz https://synthetic-packages.s3.amazonaws.com/Chromium/rpm/chromium-131.0.6778.204-1.el9.tgz
You can verify the authenticity of the packages using the signature files stored together with the package archives.
Extract the installation packages. Go to the directory where you saved the archive and run the following command:
mkdir /tmp/chromium ; tar xzf chromium.tgz -C /tmp/chromium
This creates a /tmp/chromium directory and extracts the packages into it.
Install extracted packages.
sudo yum install -y /tmp/chromium/*.rpm
This installs all the packages extracted to the /tmp/chromium/ directory. You can delete the /tmp/chromium/ directory and the downloaded chromium.tgz archive after successful Chromium installation.
Disable automatic update of Chromium packages:
sudo yum -y install yum-plugin-versionlocksudo yum versionlock chromiumsudo yum versionlock chromium-common
Optional Install non-Latin TrueType fonts:
sudo yum install dejavu-fonts-common.noarch dejavu-sans-fonts.noarch
After you satisfy the dependencies, run the ActiveGate installer with root rights with the --enable-synthetic parameter set to manual. For example:
/bin/bash ./Dynatrace-ActiveGate-Linux.sh --enable-synthetic=manual
You can verify the authenticity of the packages using the signature files stored together with the package archives.
Unlike Chromium on other distributions, Chrome for Testing updates do not use package managers. You manually manage the Chrome binaries while dependencies are managed by the system package manager.
On Ubuntu Server 20.04 and 22.04 Chrome for Testing is supported since 1.331
Set up repositories and install dependencies.
Install Synthetic engine dependencies:
sudo apt-get update && sudo apt-get -y install xvfb x11-xkb-utils xfonts-100dpi xfonts-75dpi xfonts-scalable libnss3-tools auditd unzip
Install Chrome for Testing dependencies:
sudo apt-get -y install libasound2t64 libatk-bridge2.0-0t64 libatk1.0-0t64 libcairo2 libcups2t64 libgbm1 libnspr4 libnss3 libpango-1.0-0 libxcomposite1 libxdamage1 libxfixes3 libxkbcommon0 libxrandr2
Download and set up Chrome for Testing.
Create the Chrome for Testing directory:
sudo mkdir -p /usr/lib/chrome_for_testing
Download the Chrome for Testing package archive to a temporary location. This is a safe and verified archive hosted by Dynatrace.
curl --output /tmp/chrome.zip https://synthetic-packages.s3.amazonaws.com/Chrome/chrome-for-testing-linux64/chrome-for-testing-linux64-143.0.7499.192.zip
curl --output /tmp/chrome.zip https://synthetic-packages.s3.amazonaws.com/Chrome/chrome-for-testing-linux64/chrome-for-testing-linux64-142.0.7444.175.zip
curl --output /tmp/chrome.zip https://synthetic-packages.s3.amazonaws.com/Chrome/chrome-for-testing-linux64/chrome-for-testing-linux64-141.0.7390.122.zip
You can verify the authenticity of the packages using the signature files stored together with the package archives.
Extract the installation package and clean up:
sudo unzip /tmp/chrome.zip -d /usr/lib/chrome_for_testingrm /tmp/chrome.zip
This creates a chrome-linux64 directory inside /usr/lib/chrome_for_testing and extracts the Chrome binary and supporting files into it.
Verify Chrome for Testing by checking the version:
/usr/lib/chrome_for_testing/chrome-linux64/chrome --version
Command output should show the Chrome version you downloaded.
After you satisfy the dependencies, run the ActiveGate installer with root rights. The installer will automatically detect and validate Chrome for Testing. For example:
/bin/bash ./Dynatrace-ActiveGate-Linux.sh --enable-synthetic=manual
Custom Chrome for Testing directory: If you want to use a different directory than the default /usr/lib/chrome_for_testing, specify it by setting the synthetic_chrome_for_testing_path property in the custom.properties file after installation. The new directory will be used after the upgrade of Synthetic module.
Chrome for Testing files are preserved during ActiveGate uninstallation. If you uninstall the ActiveGate, the Chrome for Testing directory and its contents will remain on the system and can be reused during reinstallation.
You can verify the authenticity of the packages using the signature files stored together with the package archives.
If you have an offline environment or you installed an ActiveGate manually for dependency management or due to limited access to Amazon S3, you need to update the browser and dependencies manually.
You need to update the browser manually per ActiveGate, and the process varies slightly based on the operating system. Note that manual update of the browser only applies to Linux-based ActiveGates; on Windows-based ActiveGates, the browser is automatically updated during Synthetic engine updates.
Prerequisites:
https://synthetic-packages.s3.amazonaws.com to access the browser packages.Since ActiveGate 1.331, on Ubuntu Server 20.04 and 22.04 we use Chrome for Testing. Chromium snap distribution is no longer supported. If you are using any automation for updating the browser, convert it to use Chrome for Testing. Please refer to community guide for details.
This section is only relevant for releases 1.329 and earlier for Ubuntu Server 20.04 and 22.04.
If your ActiveGate and Chromium versions are out of support or have not been updated for several releases, review the Synthetic Engine and Chromium dependencies, and reinstall them if necessary. See the manual installation instructions for Ubuntu Server.
Download the snap (Ubuntu Server 20.04 and 22.04) package archive. This is a safe and verified archive hosted by Dynatrace at https://synthetic-packages.s3.amazonaws.com. Be sure to use the specific command provided for your ActiveGate and Ubuntu Server versions in the manual installation instructions for Ubuntu Server.
Extract and install the downloaded packages. Be sure to use the correct installation command for your Ubuntu Server version (check the manual installation instructions for Ubuntu Server).
Verify Chromium update by running the following command from the default installation directory. Command output should match the Chromium version you installed.
/opt/dynatrace/synthetic/browser --version
ActiveGate version 1.243+ In addition to web UI-guided ActiveGate installation and manual installation of the browser and dependencies, you can also install ActiveGate by pointing to a custom, local repository for browser components. As this repository is an HTTP server that you set up within your network, the advantage of this method is that it can be used in environments with intranet-only or limited network access.
This method of installing the browser broadly consists of:
Download the browser components—the package archive and signature file—from the safe and verified archive hosted by Dynatrace. See Requirements for private Synthetic locations for links to the latest supported and provided browser versions.
We recommend keeping your Linux-based Synthetic-enabled ActiveGates and browser versions up to date; choose the latest provided browser version for ActiveGate.
For example, for ActiveGate version 1.331 on Ubuntu 24 the required files are:
https://synthetic-packages.s3.amazonaws.com/Chrome/chrome-for-testing-linux64/chrome-for-testing-linux64-143.0.7499.192.ziphttps://synthetic-packages.s3.amazonaws.com/Chrome/chrome-for-testing-linux64/chrome-for-testing-linux64-143.0.7499.192.zip.sigThe corresponding download commands are:
curl -o chrome-for-testing-linux64-143.0.7499.192.zip https://synthetic-packages.s3.amazonaws.com/Chrome/chrome-for-testing-linux64/chrome-for-testing-linux64-143.0.7499.192.zip
curl -o chrome-for-testing-linux64-143.0.7499.192.zip.sig https://synthetic-packages.s3.amazonaws.com/Chrome/chrome-for-testing-linux64/chrome-for-testing-linux64-143.0.7499.192.zip.sig
Install a web server of your choice and create a directory, for example, chromium-repo, to serve the Chromium components to the ActiveGate host. Copy the downloaded browser components to this directory.
Download the ActiveGate installer from Dynatrace Hub.
Resolve all dependencies and enable repositories as required as shown in Install the browser and dependencies manually from S3 above. The custom repository can be used only for browser packages, not their dependencies.
Install the ActiveGate with the Synthetic module enabled (--enable-synthetic) and the DYNATRACE_SYNTHETIC_CUSTOM_CHROMIUM_REPO environment variable pointing to the location of the custom repository (https://172.18.0.100/chromium-repo in this example).
sudo DYNATRACE_SYNTHETIC_CUSTOM_CHROMIUM_REPO=http://172.18.0.100:8000/chromium-repo /bin/bash Dynatrace-ActiveGate-Linux-x86-*.sh --enable-synthetic
You can use the hostname of the HTTP server instead of the IP address so long as the ActiveGate host can resolve the hostname.
Once you've installed the browser in this way from a custom repository, it can only be autoupdated. See Browser autoupdate from a custom repository in Manage private Synthetic locations for details and update alternatives.
If you've enabled a custom, local repository for the browser installation, the browser can only be autoupdated. Follow this procedure to autoupdate the browser via the same custom repository.
After ActiveGate installation, specify the custom repository of the ActiveGate in the [synthetic] section of the custom.properties file in the /var/lib/dynatrace/gateway/config directory. This allows for automatic browser updates from the custom repository during manual or automatic Synthetic engine updates.
[synthetic]chromium_repo = https://172.18.0.100/chromium-repo
Turn on Enable Chrome(-ium) auto-update for your private location.
Note that the browser autoupdate UI setting applies to all ActiveGates assigned to your private location.
Ensure that the browser components required for update are available at the custom repository location. The browser is then automatically updated from the custom repository during ActiveGate and Synthetic engine updates.
If you do not specify the custom repository in custom.properties, the browser is downloaded and updated from S3 during a manual or automatic ActiveGate and Synthetic engine update.
You can install a custom browser version, that is, override the browser version that the ActiveGate installer looks for. This is applicable for manual ActiveGate installation, as described in Browser installation via S3 or via a custom repository.
In this command for manual ActiveGate installation via S3, an environment variable points to an explicit browser version number 143.0.7499.192, which is part of the Chrome for Testing package archive.
sudo /bin/bash -c "export DYNATRACE_SYNTHETIC_EXPLICIT_CHROMIUM_VERSION=143.0.7499.192; /bin/bash Dynatrace-ActiveGate-Linux-x86-*.sh --enable-synthetic"
This command searches for the browser version 143.0.7499.192 in the custom repository https://172.18.0.100/chromium-repo.
sudo DYNATRACE_SYNTHETIC_EXPLICIT_CHROMIUM_VERSION=143.0.7499.192 DYNATRACE_SYNTHETIC_CUSTOM_CHROMIUM_REPO=http://172.18.0.100:8000/chromium-repo /bin/bash Dynatrace-ActiveGate-Linux-x86-*.sh --enable-synthetic