OneAgent

Java

• Support added for Oracle Java 11
• Support added for OpenJDK 11
  There is a known issue with jdk-11.0.1+13 this will be fixed in upcoming releases.
• Support added for reactor-netty 0.6 and 0.7
• Support added for Spring WebFlux

• We’re working towards more advanced topology monitoring for web server services and their child processes. With release version 1.155, we’re introducing a change in how processes spawned by web servers are grouped. To date, PHP and .NET worker processes were grouped together with parent web server Process Group Instances (PGI). Beginning with OneAgent version 1.155, such processes form their own PGIs. Any currently existing web server PGIs will continue to be reported by Dynatrace. However, you’ll see new PHP and .NET PGIs, and their related metrics will no longer be included in the web server PGI metrics.
• We continue to work on better management of resources consumed by OneAgent. In version 1.155 we’ve focused on disk management topics related to memory dumps. Memory dumps are now immediately deleted from disk once they’re uploaded to Active Gate. When an upload isn’t possible, memory dumps will be stored on disk, up to 20 GB for up to 2 hours. This should address use cases where Dynatrace Support assistance is needed to adjust aging configurations to allow larger memory dumps. It will also reduce the resource consumption of disk space by OneAgent.
• OneAgent version 1.155 also contains multiple improvements to memory management.
• OneAgent now detects Kafka technology automatically.
• OneAgent now detects Oracle Enterprise Linux distribution.
• We’ve improved the heuristics for detecting Azure cloud, HAProxy processes, NGINX processes, and KVM virtualization.
• We continue to work on the GA release of full-stack OneAgent for AIX operating system. The public Beta program was announced in May 2018. We continue our effort to improve the performance of metric gathering on AIX. In version 1.155, we’ve focused on reading process sockets. This and many other performance-related changes on AIX were also backported to version 1.151 and all customers participating in the OneAgent full-stack Beta are encouraged to upgrade to at least version 1.151.
• We continue to invest heavily in OneAgent installation and upgrade process reliability and automation. Most of these changes are invisible to users. Among those that are visible is improved notification of concurrent attempts of OneAgent updates. We’ve also worked towards a better (single MSI) architecture of the OneAgent installer for Windows.
• We’ve extended SELinux policy of OneAgent to also work with Fedora 28.
• We’ve improved the sorting of process properties on process overview pages.
• The kernel threads graph for AIX now provides an additional series that depicts the number of logical CPUs. This helps in kernel threads data interpretation, specifically around the detection of waiting threads.
• We’ve introduced major changes in process topology discovery. Outgoing port reuse handling has been rewritten, allowing proper interpretation of port reuse over time for timeframes shorter than 30 seconds. Moreover, we’ve improved the precision of analysis of the first few seconds of new TCP sessions. As a result, packets captured near the beginning of TCP sessions are now better represented within Process connections view (available by clicking Analyze process connections on any Host overview page).

OneAgent support changes

• 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 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).
• 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 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
• PHP 5.6 support will have end of life in April 2019

Cloud Platform support

• Dynatrace has once again extended its capabilities for monitoring Cloud Foundry foundations and now provides dedicated built-in Cloud Foundry overview pages.
• Dynatrace fully supports RedHat OpenShift 3.11 clusters with underlying Docker container runtime. CRI-O support will come soon.
• Added support for Application-only integration of OneAgent during run-time of pods for Kubernetes and OpenShift based on InitContainers.
• Added support for Application-only integration of OneAgent during build-time for Kubernetes based on multi-stage Docker builds. Dynatrace ActiveGate now supports the download of OneAgent code-modules as Docker image layers. You can use an ActiveGate as a Docker registry for multi-stage Docker builds.
• OneAgent now detects the project your instance is running in Google Cloud Platform. You can leverage the project information in all tagging, renaming, detection rules, and Management zones. For details, see the blog post about Google Cloud Platform properties.
• Dynatrace OneAgent reports the detected Cloud platform type for hosts. For example, Dynatrace automatically detects if a host belongs to a Cloud Foundry, OpenShift, or Kubernetes environment.
• OneAgent further automatically detects if BOSH was used for provisioning and deploying software on a VM.

Real User Monitoring (JavaScript)

• Angular 7 was released in October 2018.  We’re happy to announce support of Angular 7 beginning with version 1.155. In addition, Angular JS 1.7 is now also supported.
• Major improvements for Visually complete metric calculation have been made. Visually complete now supports CSS images in iframes. For details, see Important changes to Visually complete calculation.

ActiveGate

• ActiveGate on Linux now installs itself using the non-admin dtuserag user by default.
• Cloud Foundry monitoring is now enabled by default. We’ve also improved the way Dynatrace queries the Cloud Foundry API and the initial limit of 100 organizations per Cloud Foundry foundation does not apply any longer. Please also refer to Dynatrace Help for further details on connecting your Cloud Foundry foundations to Dynatrace.
• It’s now possible to better handle the ActiveGate maximum memory limit. We implemented the first part of this solution in version 1.153, but in version 1.155 it’s fully complete. By default, all new installations of ActiveGate will allocate 80% of physical memory to ActiveGate processes. In case of upgrades from older versions of ActiveGate, the previous default setting for maximum memory will be preserved and stored in the launcheruserconfig.conf file as a custom memory setting. If, however, the default for the memory setting was manually changed in prior versions of ActiveGate, the older settings will be overwritten and the new default might need to be verified by your admin and potentially stored as a custom setting. Starting with version 1.155, this setting will be preserved across consecutive ActiveGate updates.

Important bug fixes

• APM-139857 – OSAgent’s log contained debug information about AppDomains, despite debug flag not being set.
• APM-133379 – OneAgent Watchdog was crashing in some cases.
• APM-139449 – OneAgent installer for Windows was failing on creation of internal MSI log file.
• APM-142058 – We fixed invalid permissions on custom installation path causing Java deep code monitoring module injection failures.
• APM-142216 – Watchdog was trying to start non-existent plugin and log analytics modules on AIX. This fix was backported to version 1.149.
• APM-142744 – We have fixed minor memory leaks in OneAgent install and update processes.
• APM-143561 – In some cases the OSAgent module of OneAgent was not able to send pings to OneAgent Watchdog, which resulted in Watchdog incorrectly assuming OSAgent crash.
• APM-148478 – Gathering metrics for Docker Containers are now more resilient to Docker API timeouts