- Support added for Tibco BusinessWorks JMS to Soap binding
- General availability (GA) for F# support including end-2-end tracing using asynchronous workflows.
- We’re starting two new Early Access Programs (EAP) for IBM Message Queue tracing as well Azure ServiceBus tracing.
- Injection into .NET processes has been greatly improved, especially in cases of so-called “lazy CLR initialization.”
- Starting with OneAgent 1.157, OneAgent SDK for .NET version 1.1.0-alpha (Early Access) now supports tracing of remote calls. This version is no longer compatible with earlier OneAgent versions.
- Support for MySQL2 (beta)
- End of beta phase, General availability
- Support for Go 1.10.1
- It’s now possible to see all the VMs for individual ESXi hosts without drilling into any specific resource utilization category. The VMs are sorted based on the resource dimension (CPU usage, memory, etc.) selected in the main infographics.
MACVLANnetwork mode is now reported for Docker on Linux.
- Network mode
CONTAINERis now detected and the reference to the actual network mode is provided.
- Gathering metrics for Docker Containers is now more resilient to Docker API timeouts.
- Docker image version is now written to the log in case OneAgent is deployed as a container.
- OneAgent for AIX is now capable of detecting and naming Oracle processes.
- OneAgent for Windows and Linux is now capable of detecting and naming DB2 processes.
- The performance of OneAgent on AIX operating system has been greatly improved, especially during the process of socket readout.
- OneAgent now properly reports on disk statistics when it’s deployed as a container on Google Container Optimized OS (Google COS).
- OneAgent blacklists entire Process Group Instances (PGI) only when the main process matches one of blacklist filters.
- We now report the parent-child relationship between IIS and .NET Core on Windows.
- OneAgent for AIX now skips the unnecessary update check for plugins.
- The OneAgent file aging mechanism now logs all removals of support alerts, memory dumps, and crash alerts.
- AliyunKVM is now discovered and labeled as KVM.
- OneAgent provides IIB version information for detected IIB processes.
- We’ve greatly improved the OneAgent installation and auto-update processes. Most of these changes are transparent to users, though they play a key role in the robustness of OneAgent rollout and updates. Additionally, we’re continuously improving OneAgent self-diagnostics so that our Support team can diagnose and fix potential problems faster.
- The OneAgent EXE Installer for Windows now asks for elevated privileges when starting.
- The OneAgent EXE Installer for Windows now returns a proper exit code on failure.
- We’ve improved how the OneAgent uninstallation process returns the system to the original state when symlinks are used for runc binaries.
OneAgent support changes
Dynatrace OneAgent support for 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 31th April 2018)
OneAgent version 1.157 will be the last version that supports Node.js 4 (release planned for the end of 2018).
- Node.js 9 (EOL by Node.js 30th June 2018)
OneAgent version 1.157 will be the last version that supports Node.js 9 (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 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
- PCF version v2.1.x (Pivotal will discontinue support for this version by end of December 2018. Please consult Pivotal’s support matrix for further details.)
OneAgent version 1.163 will be the last version that supports PCF version v2.1.x (release planned for March 2019).
- PHP 5.6 support will have end of life in April 2019
Cloud platform support
- Dynatrace fully supports vanilla Kubernetes 1.12 clusters with underlying Docker container runtime. CRI-O support will come soon.
- We’ve published a new Dynatrace OneAgent BOSH release that provides support for Xenial stemcells. You can access the v1.1.0 release here.
- We’re starting Early Access Program (EAP) for monitoring additional AWS services.
- Dynatrace fully supports Pivotal Cloud Foundry versions 2.3 and 2.4. You’ll find further details about the Dynatrace support model for Pivotal Cloud Foundry full-stack monitoring here. Please note that Pivotal Cloud Foundry 2.3 and 2.4 both require the new OneAgent BOSH release v1.1.0.
- Added support for importing AWS CloudTrail logs. Requires Environment ActiveGate 1.157 and cluster 1.158 or higher.
- Added the ability to import logs to central log storage by means of syslog or API. Requires Environment ActiveGate 1.157 and cluster 1.158 or higher.
Important bug fixes
With this release of OneAgent and ActiveGate, we’ve resolved the following issues:
- APM-134999 – We have fixed the incorrect process connection reported to have occurred on a host with ActiveGate.
- APM-141516 – Calls to Docker API were failing or being blocked by multiple nested exceptions on OpenShift.
- APM-143075 – Websphere name was misdetected when command line exceeded 4096 characters
- APM-144881 – We have improved the restart of OneAgent which in some cases resulted in exception in the logs while monitoring .Net processes
- APM-145479 – We have fixed the naming of the wrapper script in case of HAProxy process group.
- APM-146361 – PHP-CGI processes were grouped into one PGI even if they were coming from different IIS application pools.
- APM-146724 – Fixed OneAgent’s watchdog segmentation fault in the very unlikely case of race conditions.
- APM-147657 – Fixed a situation where OneAgent’s installer for AIX was freezing during auto-update process.
- APM-148200 – Large Memory Dumps were immediately deleted on OneAgent in some cases, preventing them from being uploaded for analysis.
- APM-148630 – OS Agent logs were incorrectly warning about missing startup timestamp of
- APM-149745 – We were missing log message when calculating memory limit for ActiveGate during initial startup of Watchdog.
- APM-153137 – When installed in non-privileged mode on Linux, the installer could have sent termination signal to itself leading to host being lost during AutoUpdate.
- ONE-17746 – Disk mount points were not matching real layout in case of Google COS.