Deploy ActiveGate in a VM for OpenShift monitoring

If you want to monitor several OpenShift clusters with one ActiveGate and don't need to separate networks for administrative or operational traffic, you can deploy a classic ActiveGate in a virtual machine to connect your clusters to Dynatrace as described below.

1. Start installation

Sign in to Dynatrace, select Deploy Dynatrace from the navigation menu and select Install ActiveGate.

2. Download the installer

How you download your installer depends on your setup and needs. You can choose to download an installer directly to the server where you plan to install Environment ActiveGate or you can download an installer to a different machine and then transfer the installer to the server.

  1. Select the ActiveGate purpose.

  2. Select Download installer.
    If you plan to download Environment ActiveGate directly to the server, make sure your system is up to date, especially SSL and related certificate libraries. Outdated libraries (for example, CA certificates) or missing OpenSSL will prevent the installer from downloading (Dynatrace uses encrypted connections, so OpenSSL is required to enable wget to access the server).

    • Download the installer using one of these options:
      • Run the command
        Copy the wget command from the text box and paste it into a terminal window on the machine where you plan to install the ActiveGate. Make sure you copy the command directly from the first text box; it contains your environment ID.
      • Download via browser
        No internet access on servers? You can download the installer by selecting the ActiveGate installer link at the bottom of the page and saving the installer script to any location on your system, thereby bypassing the wget command altogether.
  • Verify the signature
    Wait for the download to complete. Then verify the signature by copying the command from the second Verify signature text box and pasting the command into your terminal window.

3. Run the installer

An install parameter (determined by the ActiveGate purpose you selected) is automatically set for the command to run the installer. Make sure you use the command displayed in the Dynatrace web UI that reflects the ActiveGate purpose.

Copy the installation script command from the Run the installer with root rights step and paste it into your terminal.

You only need root rights to install an ActiveGate. The user running the ActiveGate service doesn't require root rights. If you don't specify your own user to run the ActiveGate service, the installer will create and use the dtuserag user by default.

To install ActiveGate, run one of the following pairs of commands in the directory where you downloaded the installation script.

  • Ubuntu Server

    [user@ubuntu]# chmod + x  
    [user@ubuntu]# sudo ./
  • Red Hat Enterprise Linux

    [user@rhel]# chmod + x  
    [user@rhel]# su ./
  • Other Linux distribution with root session

    [root@host]# chmod + x  
    [root@host]# ./

4. Connect your OpenShift clusters to Dynatrace

To connect the Kubernetes API to Dynatrace

  1. Create a service account and cluster role.

Create a service account and cluster role for accessing the Kubernetes API. This creates the bearer token necessary to authenticate in the Kubernetes API. Use the following snippet.

oc apply -f
  1. Get the Kubernetes API URL.
$ oc config view --minify -o jsonpath='{.clusters[0].cluster.server}'
  1. Get the bearer token.
oc get secret $(oc get sa dynatrace-monitoring -o jsonpath='{.secrets[0].name}' -n dynatrace) -o jsonpath='{.data.token}' -n dynatrace | base64 --decode
  1. In the Dynatrace menu, go to Settings > Cloud and virtualization > Kubernetes.
  2. Select Connect new cluster.
  3. Provide a Name, the Kubernetes API URL, and the Bearer token for the OpenShift cluster.
  4. Turn on Enable monitoring and Show workloads and cloud applications.

In Dynatrace environments earlier than version 1.190, you need to turn on Cloud application and workload detection in Process group detection settings. This way, cloud applications and workloads will be detected properly and process groups won't be spread across different cloud applications and workloads.

  1. Select Connect to save your configuration.