OneAgent & Security Gateway release notes v1.141

OneAgent

Solaris

Solaris support for Java & Apache HTTP Server now generally available.

Java

• Support for OkHttp Java client 3.x
• Support for the PEGA wrapped Apache Http Clients

Node.js

• Added support for Couchbase
• Event loop monitoring has been extended with a time series for active handles
• Node.js applications started from the same directory are now distinguished by their start script names

Go

• Added support for versions 1.7.5, 1.7.6, 1.8.7, and 1.9.4.

General improvements and fixes

• Added support for non-root mode deployment on Linux. This feature is provided as a public beta starting with OneAgent v1.141. It enables OneAgent on Linux to be deployed in environments that are governed by strict security regulations. For details about this and other important features see new & upcoming OneAgent improvements.
• Full-stack OneAgent for the AIX operating system is provided as a public beta. Read more about this release at OneAgent full-stack monitoring available for AIX.
• Within Linux deployments, you can manually specify the user group for OneAgent to operate on. To specify the group parameter, OneAgent installation must be invoked using theGROUP and USER parameters. Note that the group provided in the GROUP param must be a primary group of the user provided in the USER param.

$ sudo ./Dynatrace-OneAgent-Linux.sh GROUP=groupname USER=username

• The hostautotag.conf file is now re-read whenever changes are made to the file. This modification allows for scripted and/or automatic tagging of hosts in Dynatrace. This file is automatically created during installation and is placed in the OneAgent config folder (on Windows, %PROGRAMDATA%\dynatrace\oneagent\agent\config, and on Linux and AIX, /var/lib/dynatrace/oneagent/agent/config). The hostautotag.conf file contains the key/value pairs, which are interpreted the same way as the TAGS environment variable.
• It’s now possible to define custom properties per host using the configuration filehostcustomproperties.conf, which is located in the OneAgent config folder. Similar to host tags, this file contains the key/value pairs.
• OneAgent correctly detects and names Redis processes on Windows.
• Added the PHP monitoring module musl-libc flavor to the Linux full-stack installer.
• New model of disk reporting: OneAgent now reports block devices instead of mountpoints.
• New ID calculation model for Cloud Foundry. This change impacts how PGIs are identified and in some cases may cause PGIs to be re-created with new IDs.
• Resolved a number of bugs and implemented smaller corrections related to:
  • The installation process, specifically focusing on preceding system checks, updates, user account handling, watchdog operation, and uninstallation process cleanup;
  • Data collection, specifically focusing on service deployment detection, disk metrics, CPU calculation, and host identification;
  • Stability and CPU consumption reduction of Dynatrace OneAgent.
• With the next release, support for Alpine Linux (musl-libc) will be reduced to container environments only (for example, when integrating Dynatrace OneAgent into OpenShift or Kubernetes application containers).
• Public beta release of the Heroku buildpack for Dynatrace OneAgent. The buildpack for Dynatrace OneAgent enables cloud-native monitoring of Heroku applications by integrating Dynatrace OneAgent into the application’s slug and dyno.

Security Gateway

• Added support for Amazon Linux as host operating system for Security Gateway. To learn more about supported operating systems and versions please consult the supported technologies page.
• Better handling of concurrent queries to AWS APIs.