Update Dynatrace Managed

To run a successful update, you need at least 3 GB of available space on the partition where Dynatrace Managed is installed.

Update of Dynatrace Managed consists of two steps:

  1. Downloading the update package.
  2. Performing the actual update.
Sequential updates

Updates of Dynatrace Managed can only be done sequentially with regard to versions. If your Dynatrace Managed cluster currently runs for example, version 1.146 and you want to upgrade it to version 1.150, you'll have to upgrade first to version 1.148 and then to version 1.150.

Package download

Typically, the update package download occurs automatically. If you wish to download the update packaged manually, the automatic download can be disabled on demand only via the Mission Control.

For servers not connected to Mission Control (offline servers), upon update release, you will receive an official email with a link to download the update package.

For automatic updates, all you need to do is specify a convenient time when your users won't be using Dynatrace Managed and the system can upgrade itself (for example, during a previously scheduled maintenance window).

Update in progress

Your monitoring and cluster management pages won't be accessible during the upgrade process if your cluster consists of only two nodes or the upgrade requires a restart of all nodes simultaneously (rare occurrence).

To define a start time for automatic updates:

From the navigation menu, select Settings > Automatic update.

Set the Install Dynatrace cluster updates automatically switch to the On position.

Cluster license

This switch is disabled if the license for the cluster has the Enforce automatic cluster updates feature enabled. In such cases, even the cluster administrator can't change this setting.

Specify a weekly maintenance window start time. Dynatrace Managed updates will start at the time you specify.
This setting doesn't affect the download of updates.

Manually triggered update

For manually triggered updates, you have to trigger the actual update with the user interface or via the REST API. Once triggered, the update process is performed in the same way as in the automatic updates. Typically, you would use the manually triggered update if you wish to initiate the update outside scheduled maintenance window.

Offline cluster update

Offline cluster is a cluster with a specific license that permits this cluster to operate in closed environments. These clusters are administered by Cluster Management Console (CMC). Once the update is announced, you will receive an email with a link to download the update package.

To update an offline cluster:

Download the update package from the official source to the node.

Use the Cluster Management Console (CMC) to upload the patch to the cluster.
The Cluster Management Console will propagate the update package to all the nodes and execute the update in the same way as in the automatic updates.

Manual update

For manual update, you must manually download the update package, manually propagate the update package to all your cluster nodes, and manually initiate the update script.

Update nodes in sequence

Since the node that's being updated isn't operating, it's crucial that you manually update in sequence.
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:

Download the update package from the official source to the node.
You can copy the update package into any convenient path on the node system.

Give the update package executable permissions. Use Linux chmod command.

[root@localhost]# chmod +x update_package.sh

As a root user, execute the update script with the --upgrade parameter.
Once the update completes successfully, move to the next node and repeat the procedure.

[root@localhost]# ./update_package.sh --upgrade

Dynatrace Managed version check

To check which Dynatrace Managed version you currently use:

Log into the Cluster Management Console or one of your monitoring environments.

Open the User menu in the top right corner. The version number appears at the bottom right corner of the User menu.


Navigate to the home page of your Cluster Management Console, where you can view your Dynatrace Managed deployment status.

Click a Dynatrace Managed node to open the overview page of this node. The installed version appears right under the title of the page.

ActiveGate update

One-click update is supported for both cluster and environment ActiveGates (including ActiveGates enabled for multi-environment support). To use one-click update you must have:

  • Dynatrace version 1.177
  • ActiveGate version 1.177

You can automatically download and start the ActiveGate update process with just one click on the Deployment status page.

Deployment status page showing ActiveGates to be updated

Instead of remotely logging in to the machine hosting the ActiveGate, check which ActiveGate version you've installed and update to the latest version.

To check your installed version and update to the latest version

  1. Select Deployment status from the navigation menu.
  2. Select ActiveGates to see the list of hosts that have ActiveGates installed on them, along with their versions.
  3. Expand any host entry to see the properties and capabilities of the ActiveGate.
  4. Click the Update ActiveGate button to trigger automatic update to the latest version.
Deprecated versions

Support for ActiveGate versions 1.154 and earlier was deprecated with the release of Dynatrace version 1.184.

If you have ActiveGate version 1.154 or earlier, perform a manual update to at least ActiveGate version 1.177, which supports one-click update.

red error exclamation icon The red warning icon indicates that your ActiveGate is older than version 1.154. You should update these ActiveGates immediately because, starting with Dynatrace version 1.184, these ActiveGates will no longer be supported or work.

yellow exclamation warning icon The yellow warning icon indicates that your ActiveGate is behind by more than five versions. You should update these ActiveGates as soon as possible.

The version number in the Version column represents the ActiveGate version, not the versions of the capabilities running on the ActiveGate. When only a capability is updated, that ActiveGate version number doesn't change. As a result, the ActiveGate version number will remain unchanged until you update the actual ActiveGate, not just its individual capabilities.

One-click update doesn't require a reboot of the ActiveGate host.