OneAgent

Java

• Added initial support for TIBCO BusinessWorks 6.4
  • End-to-end tracing via web requests and JMS
  • Process group detection of TIBCO BusinessWorks 6.4 applications based on Domains, Spaces, and App Nodes. To enable, go to Settings > Process groups >Process group detection and enable the TIBCO BusinessWorks engines setting.
    
• Added support for Software AG WebMethod Integration Server 9.x and 10.x
  • Added support for end-to-end tracing via WebMethod Broker and WebMethod universal messaging
• Added support for Wildfly 13 and 14

.NET

• OneAgent SDK for .NET for custom tracing is now available to all customers as an open EAP release.

Node.js

• Added support for gRPC end-to-end tracing (beta).

PHP

• …

Docker

• Monitoring of Windows Server Containers (Docker for Windows) has been improved with better detection of executable paths.
• Docker topology on Linux is now also reported in cases when OneAgents are deployed in cloud infrastructure monitoring mode.

General improvements

• OneAgent is now officially validated for proper installation on Fedora 28.
• OneAgent uninstallation on Linux now properly restores runc configuration.
• With OneAgent for AIX, it’s now possible to use OpenSSL enc instead of uudecode during install and update procedures. The absence of uudecode and the presence of enc is automatically detected.
• OneAgent now properly detects Google Cloud Platform host IP addresses as well as projects from Google metadata.
• OneAgent now properly parses run options for HAProxy monitoring.
• OneAgent version 1.153 now provides new measurements for AIX LPAR hosts. With the introduction of kernel threads, it’s now easier to identify a logical partitions’ oversubscription to computation power, specifically in the area of logical CPUs. The additional counters for blocked threads suggest areas for potential reconfiguration.
  

OneAgent support changes

• Java Virtual Machine 5 (all vendors, EOL by Oracle on May 31, 2015)
  OneAgent version 1.157 will be the last version to support this (planned for the end of 2018).
• Node.js 4 (EOL by Node.js 31 in April 2018)
  OneAgent version 1.157 will be the last version to support this (planned for the end of 2018).
• PCF versions 1.10.x, 1.11.x, and 1.12.x. Pivotal has already discontinued support for these versions. Please consult Pivotal’s support matrix for further details.
  OneAgent version 1.157 will be the last version to support this (planned for the end of 2018).
• Kubernetes versions <= 1.6 are no longer actively maintained by the Kubernetes community.
  OneAgent version 1.153 will be the last version to support this.
• OneAgent deployment on the following operating system versions for which the respective providers have discontinued support. OneAgent version 1.157 will be the last version to support these.
  • Ubuntu 12.04, 12.10, 13.04, 13.10, 14.10, 15.04, 15.10, 16.10, 17.04 (14.04 LTS, 16.04 LTS, as well as 17.10 and above will continue to be supported)
  • Debian 6
  • Fedora 20, 21, 22, 23, 24, 25
  • openSUSE 12.1, 12.2, 12.3, 13.1, 13.2, 42.1, 42.2
  • Windows 8

Cloud platform support

• Dynatrace OneAgent now automatically detects Cloud Foundry hosts of technology type Diego cell. You’ll find this information as part of the Technologies host level property
• The new technology type Diego cell is also available for auto-tagging, host and process group naming rules, and management zones.
• Dynatrace OneAgent automatically derives tags and metadata from Cloud Foundry and Kubernetes environments and attaches it on respective processes. These tags and metadata (i.e., Kubernetes annotations) are now also automatically propagated to related services.
• Dynatrace OneAgent can now also automatically monitor Golang applications without code changes in locked-down app-only scenarios. For details, consult Dynatrace documentation for app-only monitoring in Kubernetes, OpenShift, Google App Engine, and Heroku environments.
• Dynatrace OneAgent Operator version 0.2.0 has been released. The release includes support for OneAgent resource settings and is also available as a RedHat certified operator image in the RedHat Container Catalog.

Real User Monitoring (JavaScript)

• …

ActiveGate

• Application (ALB) and Network (NLB) load balancer types are now fully supported out-of-the-box together with the pre-existing (i.e., “Classic”) load balancer. This requires Dynatrace Server version 1.153 or higher.

Important bug fixes

• APM-136303 – non-root (non-privileged) mode of OneAgent was not correctly enabled after Linux kernel update
• APM-138047 – LZMA decompression fails because of insufficient disk space on C:, broken required free space detection
• APM-138182 – Signal was reported as error code for java application
• APM-138331 – Misleading message was printed for SELinux on CoreOS
• APM-139650 – There was no info about required and free disk space in AutoUpdate alert
• APM-139829 – Custom OneAgent plugin deployment on Windows was not working
• APM-141003 – Graceful OS shutdown was not creating a problem on Linux: OneAgent detected a manual agent shutdown instead
• APM-141248 – AutoUpdate signature verification was failing in case of OneAgent on AIX
• APM-135316 – OS Agent log was spammed with incorrect warnings on AIX: Invalid (zero) PGI identifier for type: * processgroupid_calculate() – invalid input data
• APM-136429 – OneAgent log filled with unexpected warnings for “RestartRequiredDetection – missing startup timestamp for prorocess kdevtmpfs”
• APM-137928 – OneAgent log filled with unexpected warnings “Invalid Stat Counter – PGI CPU Usage / ProcessorForTSMeasures.executeHandlerForIncomingMessage*”
• APM-133072 – Container restart required message incorrectly displayed for Windows Server Containers
• APM-138545 – Deep code monitoring module “Injection Failed” alerts were generated despite the process being blacklisted
• APM-139160 – Java instrumentation did not continue after a server reboot
• APM-139418 – Azure was not detected correctly as cloud platform
• APM-139576 – Java processes were not successfully instrumented in some cases
• APM-139739 – Processes under Docker were incorrectly recognized as ‘Go’