• Home
  • What's new
  • Release notes
  • ActiveGate
  • ActiveGate release notes version 1.187

ActiveGate release notes version 1.187

10 March, 2020

ActiveGate support changes

Due to the introduction of 64-bit host IDs, Dynatrace version 1.188 is the last version that accepts ActiveGate versions earlier than 1.154.

With Dynatrace version 1.188, ActiveGate versions earlier than 1.154 are no longer be supported.

Your action required

If you have ActiveGates older than version 1.154, update them at your earliest convenience.

Support changes

Known issues

Canceling Windows ActiveGate update will remove current installation (APM-205990)

Depending on your internet access and speed, ActiveGate update may take a long time, and the installer may appear to have stopped responding even though the installation is in progress.

Do not cancel ActiveGate update for Windows

Let the update process finish. If you cancel while the new version is still downloading, you will not have any working ActiveGate installation on this host.

Workaround

If you canceled the ActiveGate update and unintentionally removed the ActiveGate installation from your host:

  1. Make a copy of the content of the %PROGRAMDATA%\dynatrace\gateway\config folder.
    This folder contains configuration files or backups of configuration files from the removed ActiveGate.

  2. Install ActiveGate with the old configuration files still in the %PROGRAMDATA%\dynatrace\gateway\config folder.

  3. Verify that the old configuration files have been included in the current ActiveGate configuration files.
    If they are not, manually copy selected settings from your backup to the current ActiveGate configuration files.

Resolved issues

  • General Availability (Build 1.187)

General Availability (Build 1.187)

The 1.187 GA release contains 3 resolved issues.

ComponentResolved issues
ActiveGate2
Infrastructure1

ActiveGate

  • Fixed returning from "failover" mode. If ActiveGate, during start, went for a short period of time into the failover mode, in some circumstances, returning from the failover mode ended in state "waiting for configuration" instead of "running" although all modules on the ActiveGate were working correctly, except of the REST API returning ActiveGate state. (APM-216487)
  • Local user is properly created on sysV machines. (APM-218964)

Infrastructure

  • DocumentDB AWS instances CloudWatch metrics are being collected correctly now. (APM-215203)