ActiveGate release notes version 1.177
OneAgent version 1.179 will be the last version to support only 32-bit host IDs. By that time, all ActiveGates earlier than version 1.154 must be upgraded to newer releases in order to properly support OneAgent 64 bit IDs. Failure to do this will result in OneAgent being unable to communicate with the Dynatrace Cluster via these earlier versions of ActiveGate. Other than that, this change will be completely transparent.
Cloud Platform support
Now you can use up to 10 tags to limit the scope of AWS environment monitoring.
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.
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.
If you canceled the ActiveGate update and unintentionally removed the ActiveGate installation from your host:
Make a copy of the content of the
This folder contains configuration files or backups of configuration files from the removed ActiveGate.
Install ActiveGate with the old configuration files still in the
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.
General Availability (Build .177)
The .177 GA release contains 3 resolved issues.
- Improved CloudWatch metrics collection in case of topology AWS API throttling errors. (APM-194782)
- Fixed permissions to C:\ProgramData\dynatrace\gateway\config\keystore.jks. (APM-190567)
- Fixed support for SNI configuration: jsse.enableSNIExtension. (APM-190648)