OneAgent & ActiveGate release notes (version 1.151)

OneAgent

Java

  • We’ve built support for bind variable capture. This feature is only available for Dynatrace Managed version 1.152 and higher.

.NET

  • We’ve built support for bind variable capture. This feature is only available for Dynatrace Managed version 1.152 and higher.
  • We’re happy to announce public beta support for .NET Remoting and .NET MongoDB monitoring.

Node.js

  • It’s now possible to capture the request attributes of outgoing HTTP response/request headers.

PHP

  • We’ve built support for bind variable capture. This feature is only available for Dynatrace Managed version 1.152 and higher.

Docker

  • We’ve improved the internal health checks of the OneAgent installer for cases where OneAgent is deployed via containers. Consequently, installation with this approach is now more resilient.
  • There are ongoing efforts toward official support for OneAgent deployment within Google Container-Optimized OS environments. We recently announced EAP of this solution. The improvements focus on volume-based storage.

General improvements

  • Confused by the default hostnames you see in your Dynatrace environment? Now you can configure naming conventions for hosts to better ensure intuitive names within Dynatrace reports and host views. Read more about this new solution in the blog post dedicated to custom host naming improvements.
  • We’ve improved the OneAgent logging that’s performed by the watchdog. Now the termination reason is written to the logs.
  • We’ve successfully validated OneAgent for operation on SUSE Linux Enterprise Server (SLES) 15 and openSUSE 15.
  • The OneAgent auto-updater now writes additional diagnostic information to logs in cases where updates fail due to low memory on a host.
  • For AIX LPARs, we report on virtual and logical CPUs as well as SMT factor. These details are provided as host properties (see image below).
    AIX LPARS
  • We’ve improved our data-aging mechanism in cases of crash reports. Consequently, the risk of overflowing the host’s storage with crash reports has been eliminated.
  • We’ve improved the consistency of reporting of the lists of monitored hosts, specifically focusing on counters and filters on the Hosts page.

OneAgent support changes

Dynatrace OneAgent support of the following platforms and components will be discontinued within the next 6 months

  • Java Virtual Machine 5 (all vendors, EOL by Oracle May 31, 2015)
    OneAgent version 1.157 will be the last version that supports JVM 5 (release planned for the end of 2018).
  • SAP Java Virtual Machine 6 (Discontinued by SAP in December 2017 and is no longer available)
    OneAgent version 1.157 will be the last version that supports SAP JVM 6 (release planned for the end of 2018).
  • Node.js 4 (EOL by Node.js 31 April 2018)
    OneAgent version 1.157 will be the last version that supports Node.js 4 (release planned for the end of 2018).
  • PCF versions v1.10.x, v1.11.x, and v1.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 that supports these PCF versions (release planned for the end of 2018).
  • PCF version v2.0.x (Pivotal will discontinue support for this version by end of September 2018. Please consult Pivotal’s support matrix for further details.)
    OneAgent version 1.157 will be the last version that supports PCF version v2.0.x (release 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 that supports these earlier Kubernetes versions.
  • OneAgent deployment on the following operating system versions for which the respective providers have discontinued the support. OneAgent version 1.157 will be the last version that supports these earlier OS versions:
    • 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

  • RedHat OpenShift Container Platform is now supported for version 3.10.
  • Documentation for Istio service mesh configuration to allow for OneAgent egress traffic is now available.
  • You can now also leverage BOSH instance metadata for auto-tagging rules, process group naming schemes, and management zones.
  • Cloud Foundry Auctioneer processes are now automatically detected as Cloud Foundry processes (similar to the detection of Cloud Foundry Gorouter processes).
  • Google Cloud Platform properties are now fully integrated with auto-tagging rules, process group renaming rules, and management zones.
  • There are new filters available in the UI for GCE and GAE hosts
    Google Cloud Platform

Real User Monitoring (JavaScript)

  • Angular version 6 is now supported.
  • We’ve added support for jQuery versions 3.3.1 and higher.

ActiveGate

Important bug fixes

With this release of OneAgent and ActiveGate, we’ve resolved the following issues:

  • APM-133887 – OneAgent installation was causing SELinux denials for self:capability fsetid to appear.
  • APM-136003 – Agent start script was displaying illegal syntax error for the grep tool on AIX.
  • APM-136122 – OneAgent was not properly restarted after the automatic update on Windows.
  • APM-134543 – AppArmor profile was not correct in case of OneAgent deployments within Apache.
  • APM-136774 – Unhandled message leading to segmentation fault in OneAgent Watchdog is now properly handled.
  • APM-136968 – OneAgent installer for AIX was incorrectly warning about non-existent log analytics module.
  • APM-124878 – OneAgent was incorrectly detecting SAP JVM.
  • APM-130602 – OneAgent for AIX was failing and locking in startup loop during the initialization.
  • APM-133183 – OneAgent was not reporting network traffic for bonded interfaces.
  • APM-135792 – OneAgent diagnostic files did not include timestamps on AIX.
  • APM-135505 – Network metrics per process were not reported on AIX.
  • APM-135928 – Websphere process group was not detected properly on AIX.
  • APM-136275, APM-136473 – The same process groups were stored multiple times causing warnings in the OneAgent logs.
  • APM-136434 – Some exceptions were not handled properly within OneAgent.
  • APM-136879 – OneAgent was incorrectly detecting PHP_CLI and PHP_CGI process groups.
  • APM-137700, APM-137312 – Misleading information in OneAgent logs was corrected.
  • APM-124692 – ActiveGate installer on Linux had the maximum number of file descriptors set to 1024, which caused operation problems in cases of large environments.

Stay updated