Header background

Environment ActiveGates can now be updated with a single click

When monitoring large enterprise environments, the number of outgoing connections and the amount of traffic can grow enormously. Dynatrace ActiveGate helps you reduce this complexity.

ActiveGates are used in various ways in large-scale deployments. An ActiveGate acts most commonly as a proxy that routes traffic between Dynatrace OneAgent and Dynatrace Server (in Dynatrace Saas or Managed). Other common uses are running cloud API integrations, synthetic monitoring, or specialized extensions (plugins) that enrich Dynatrace data.

To make ActiveGate setup and configuration easier, we’re happy to announce one-click ActiveGate updates with Dynatrace version 1.178.

Enable your new Environment ActiveGate version more easily with just one click

Starting with Dynatrace version 1.178, Dynatrace administrators are notified about new ActiveGate versions directly on the Deployment Status page (see below).

Dployment status

Now you can act on this information immediately and initiate the ActiveGate update process with just one click.

ActiveGate update button

Under the hood, there’s an ActiveGate-update mechanism running. Instead of remotely logging in to the machine hosting the ActiveGate, you just select the button; Dynatrace takes care of the rest.

For ActiveGate versions 1.154 and earlier, we’ll display the following alert. These ActiveGate versions will no longer be supported with the release of Dynatrace version 1.184 (see Prerequisites below).

Warning for ActiveGates older than version 1.154

Prerequisites

  • Dynatrace version 1.178
  • ActiveGate version 1.177
  • Available only for Environment ActiveGates, including those configured for multi-tenant (multi-environment) support

Important

Please update ActiveGate versions 1.154 or earlier as soon as possible. We will deprecate support for ActiveGate versions 1.154 or earlier with the release of Dynatrace version 1.184. This means that these versions will no longer be accepted!

What’s next

We’re constantly improving the quality of our ActiveGates and have many new enhancements in the pipeline:

  • Display of version information for the modules running on an ActiveGate
  • One-click update for Cluster ActiveGates
  • ActiveGate update via the REST API
  • Fully autonomous update mechanism for all types of ActiveGates.

Frequently asked questions

  • Can you update older ActiveGates with a single click?

No. You can’t use one-click updates for ActiveGates older than version 1.177.

ActiveGates older than version 1.177 have to be updated manually before you can see the Update button.

  • I want to update a Cluster ActiveGate with one click. How do I do this?

At the moment, we only support one-click updates for Environment ActiveGates, including those enabled for multi-tenant (multi-environment) support.

One-click updates for Cluster ActiveGates will be added to the Cluster Management Console (CMC), although we don’t have an ETA for this.

  • I clicked the Update button, but the version number didn’t change.

The main version is only a display of the ActiveGate version, not the versions of the modules running on the ActiveGate.

When a single module is updated, the major version of the ActiveGate does not change.

We’ll provide more detailed information about module versions in an upcoming release (see What’s next).

  • Why is the yellow warning sign not shown for every update that’s available?

We don’t want to overwhelm you with warnings so we’ll display the yellow icon only when an ActiveGate is behind by more than five versions.

  • I get a red warning for an ActiveGate on the Deployment status page. How much longer can I use it?

The red warning indicates that your ActiveGate is older than version 1.154. Starting with Dynatrace version 1.184, these ActiveGates will no longer be supported or work.

  • Does the one-click update require a reboot of the ActiveGate host?

On Linux systems, no.

On Windows systems, a reboot might be required. In some cases, the Windows installer triggers a reboot, for example, because some files are in use. This reboot is done automatically.

Your feedback matters

We’re ramping up, and as always, we’re listening closely to your feedback. Please share your feedback and use cases with us in our product ideas forum.