Update Dynatrace Managed

Dynatrace Managed versions are released sequentially, but you can skip certain versions in the rollout process to update to a newer version faster. For installed Managed versions that allow for faster updates, we recommend waiting until the target version is released if you cannot complete the update process within one month.

The following table illustrates the version logic.

Installed versionCan update to version
1.3061.308
1.3041.306 (only before 1.308 is released); 1.308
1.3021.304
1.3001.302 (only before 1.304 is released); 1.304

If your installed Managed version is 1.300 and you want to update it to version 1.304, you can skip version 1.302 as soon as 1.304 is released.

If version 1.304 has not yet been released, you need to first update to version 1.302 and then to version 1.304. However, once version 1.304 is released, version 1.302 will no longer be available for download.

Please note that you can skip a Managed version only if its installed version is divisible by 4.

Yes, since Dynatrace Managed version 1.324, you have full control over which versions you update to when using the automatic update functionality.

To install each version sequentially

  1. Log in to Cluster Management Console.
  2. Go to Settings > Automatic update.
  3. Turn on Run Dynatrace cluster updates sequentially without skipping a version.

To check which Dynatrace Managed version you have currently installed

  1. Log in to Cluster Management Console or one of your monitoring environments.

  2. Open the User menu in the upper-right corner.

    The Dynatrace Managed version number is displayed at the bottom of the menu.

Alternatively, you can

  1. Log in to Cluster Management Console and select Deployment status.

  2. On the Cluster nodes tab, select a node to display its overview.

    The Dynatrace Managed version number is displayed as the value of Version.

Update Dynatrace Managed

To run a successful update, you need at least 5 GB of available disk space on the partition where Dynatrace Managed is installed. For details, see Managed hardware requirements.

Updating Dynatrace Managed consists of the following steps:

By default, installation packages are downloaded automatically from Mission Control as soon as they are available to your cluster. If you need strict control over package downloads, you can opt out from automatic download of installation packages. In that case, you need to update your license. Contact a Dynatrace product expert via live chat within your Dynatrace environment.

For air-gapped deployments (not connected to Mission Control) or when you opt out from automatic download, you will receive an email notification whenever a new installation package is available. It will contain a link to download the installation package, so you can upload it manually to your cluster.

To upload an installation package to your cluster

  1. Log in to Cluster Management Console.
  2. Go to Settings > Automatic update and select Upload.

Cluster Management Console will propagate the installation package to all nodes of the cluster. If you do not want to use the web UI, you can manually copy the extracted installation package to the <INSTALLATION_DIR>/installer/upgrade directory on each cluster node.

Automatic update during maintenance window

For automatic updates, define a suitable maintenance window in which to update Dynatrace Managed.

If your cluster consists of less than 3 nodes, Dynatrace Managed won't be accessible during the update process.

To automatically update the cluster

  1. Log in to Cluster Management Console.

  2. Go to Settings > Automatic update.

  3. Turn on Install Dynatrace cluster updates automatically during the selected maintenance window.

    This switch is turned off if your license doesn't allow you to opt out from automatic updates. To change your license allowance, contact a Dynatrace product expert via live chat within your Dynatrace environment.

  4. Define a maintenance window start time. Dynatrace Managed updates will start at the time you specify.

After an installation package is downloaded, a 24-hour waiting period is required before an automatic update can run. This means that an automatic update is attempted during the first scheduled maintenance window that occurs 24 hours after the download completes.

For example, if you download an installation package today and the maintenance window is scheduled for 1:00 AM tomorrow, your update will be executed in the following week, not tomorrow, because the 24-hour waiting period will not be finished by 1:00 AM tomorrow.

Trigger update manually

If you want to trigger the update outside the scheduled maintenance window

  1. Log in to Cluster Management Console.

  2. Go to Settings > Automatic update and trigger the update manually.

    After triggering, the update process runs like automatic updates.

Alternatively, you can trigger the update via the Cluster API v1 – Updates – Trigger Upgrade.

Manual update

For manual updates, you need to manually initiate the update script on each node. Since the node that's being updated isn't operating, it's crucial that you manually update one node at a time.

Wait until the node update completes before starting an update on the next node.

To manually update the cluster, perform this procedure for each node in sequence, one node at a time.

  1. Find the update script in <INSTALLATION_DIR>/installer/upgrade

  2. Give the update script executable permissions. Use the Linux chmod command.

    [root@localhost]# chmod +x dynatrace-managed-1.238.0.20220309-065315.sh

    1.238.0.20220309-065315 is an example installer script version. The installer script of an updated version by default is placed in <INSTALLATION_DIR>/installer/upgrade/, provided that your automatic version update process is turned on.

  3. Execute the update script as a root user. Once the update completes successfully, move to the next node and repeat the procedure.

    [root@localhost]# ./dynatrace-managed-1.238.0.20220309-065315.sh --upgrade
    [root@localhost]# ./dynatrace-managed-1.238.0.20220309-065315.sh --upgrade
    Starting Dynatrace 1.238.0.20220309-065315 installer ...              OK
    Testing connection to Dynatrace Mission Control ...                     OK
    Verifying system compatibility ...                                      OK
    Verifying disk space ...                                                OK
    Verifying Dynatrace directories ...                                     OK
    Verifying system privileges ...                                         OK
    Verifying system connectivity ...                                       OK
    Stopping Dynatrace ...                                                  OK
    Preparing system user for Dynatrace ...                                 OK
    Initializing upgrade ...                                                OK
    Checking user permissions ...                                           OK
    Checking file ownership ...                                             OK
    Downloading Dynatrace OneAgent. This may take a few minutes ...         OK
    Upgrading. This may take a few minutes ...                              OK
    Preparing connectivity settings ...                                     OK
    Setting up cluster configuration. This may take a few minutes ...       OK
    Starting Dynatrace. This may take up to half an hour ...                OK
    

    Upgrade completed successfully after 8 minutes 50 seconds.
    

    Dynatrace binaries are located in directory /opt/dynatrace-managed
    Dynatrace data is located in directory /var/opt/dynatrace-managed
    Dynatrace metrics repository is located in directory /var/opt/dynatrace-managed/cassandra
    Dynatrace Elasticsearch store is located in directory /var/opt/dynatrace-managed/elasticsearch
    Dynatrace server store is located in directory /var/opt/dynatrace-managed/server
    Dynatrace session replay store is located in directory /var/opt/dynatrace-managed/server/replayData
    You can now log into your Dynatrace Server at https://10.10.10.10
    

    [root@localhost]#