Tuesday, 16 April, 2019 UTC


Summary

Dynatrace news
OneAgent

Java

  • Added support for the Akka HTTP client API (Server API was added in OneAgent version 1.161)
  • Added support for Amazon Corretto.
  • GA release of Jetty HTTP support (non-servlet)

.NET

  • Starting with OneAgent 1.165, OneAgent SDK for .NET (version 1.3.0) provides in-process linking to trace services between thread boundaries that aren’t supported out-of-the-box.

Node.js

  • Starting with OneAgent version 1.165, OneAgent SDK for Node.js (version 1.3.0) supports end-to-end tracing for messaging.

General improvements

  • AIX full-stack monitoring is now available as a GA release 
  • An additional enhancement to OneAgent support for AIX is that we’ve modified how startup scripts are created. Given that the startup of processes is handled by inittab, we’ve placed these in the same location as in the case of systemd: /opt/dynatrace/oneagent/agent/initscripts (or <INSTALL_PATH>/agent/initscripts to be more precise). To allow for backward compatibility of this change, we’re now also creating a symlink to the init script from the old location (/etc/rc.run). This symlink will eventually be removed, so if you have any dependencies on the OneAgent for AIX startup script, be sure that OneAgent has been updated to include the new location. It’s also possible to remove this symlink manually if needed. Also note that the autostart scripts are now registered only for runlevel 2, so that OneAgent isn’t launched when an AIX host is started in maintenance mode.
  • Upon uninstall of OneAgent for Windows, some residual folders were left on the hard drive. These folders are now completely removed with the removal of OneAgent.
  • We’ve also improved the sanity checks of OneAgent, corrected some of the previously misaligned logging levels, and improved the general robustness and automation of OneAgent deployment and auto-upgrade mechanisms.
  • BOSH stemcell versions are now detected. This information allows us to detect outdated stemcell versions, which most likely are missing security updates.

OneAgent support changes

Dynatrace OneAgent support of the following platforms and components will be discontinued within the next 6 months
  • Oracle Hotspot JVM v10 (non‑LTS). Oracle discontinued Premium Support in September 2018. Please consult the Oracle support matrix for further details.
    OneAgent version 1.169 will be the last version that supports Oracle Hotspot JVM v10.
  • OpenJDK v10 (non‑LTS). Oracle discontinued Premium Support in September 2018. Redhat the primary supporter of OpenJDK has never officially supported OpenJDK v10.
    OneAgent version 1.169 will be the last version that supports OpenJDK v10.
  • PHP 5.6 support will have end-of-life in April 2019.
  • PCF PAS version v2.2.x (Pivotal support for this version ends in April 2019. Please consult Pivotal’s support matrix for further details.)
    OneAgent version 1.171 will be the last version that supports PCF version 2.2.x.
Cloud platform support

Cloud Foundry

  • As mentioned above in the General improvements section, Dynatrace OneAgent now detects the BOSH Stemcell version for CloudFoundry VMs (for example, 170.30) as well as the vendor name (for example, Pivotal). For Pivotal Cloud Foundry, we’ve also added support for the detection of PCF PAS versions, (for example, 2.4). This detection is currently limited to Linux VMs.
  • We’ve extended the Cloud Foundry overview page with a dedicated Properties tile. You’ll find the Cloud Foundry API version as well as the Cloud Foundry Build version (which represents the Cloud Foundry foundation version). These properties are gathered from the Cloud Foundry API /info endpoint.
  • In alignment with our “reduce to the max” mantra, we’ve improved the infographics that appear at the top of the Cloud Foundry overview page.
    • Cloud Foundry platform processes and application processes have been extended with a link to the related Cloud Foundry foundations. This allows for filtering of platform processes related to specific foundations on the Technology overview page and it eases navigation from the process level to the foundation level.
  • The latest release of the Cloud Foundry IBM WebSphere Liberty buildpack version 3.8, as well as Cloud Foundry PHP buildpack version 4.3.71, include minor enhancements to our Dynatrace OneAgent integration. For example, the environment variable DT_LOGSTREAM is now set to stdout by default and the calculation of the host ID is now solely done by OneAgent.
  • We’re happy to announce the general availability of the Heroku buildpack for Dynatrace OneAgent. For details, see guidelines for monitoring your Heroku applications.
  • We’ve uploaded a new minor release of the Dynatrace Service Broker tile to the Pivotal Network. Release 1.4.1 includes support for the skiperrors flag which allows for configuration of OneAgent error handling.
  • Dynatrace now also supports Cloud Foundry’s buildpack for .NET Core on Linux for monitoring your .NET Core applications that are deployed in Cloud Foundry PaaS environments. Support starts with buildpack v2.2.9.

Kubernetes

  • The OneAgent Operator version 0.2.1 release includes backports from the version 0.3.0 release for skipCertCheck and disableAgentUpdate. The new version 0.2.0 release is compatible with Kubernetes versions 1.9+ and OpenShift 3.9+.
ActiveGate
  • For Cloud Foundry monitoring, it’s now possible to configure a proxy for communication with the Cloud Foundry API. You need to adapt your custom.properties file by adding the following configuration:
    [http.client.external]
    proxy-server = <server or ip address>
    proxy-port = <port number>
    proxy-scheme = <http or https>
    proxy-user = <userid>
    proxy-password = <password>
  • For Cloud Foundry monitoring, it’s now also possible to use self-signed certificates even when they’re provided as a certificate chain. You need to adapt your custom.properties file by adding the following configuration:
    [http.client.external]
    hostname-verification = yes
    certificate-validation = yes
    Note that the self-signed certificate must be added to the trusted keystore (trusted.jks). For details, see How to install an ActiveGate.
  • ActiveGate now supports custom certificates (PKCS#12 format) rather than the default certificate. You need to adapt your custom.properties file by adding the following configuration and restarting the ActiveGate:
    [com.compuware.apm.webserver]
    certificate-file = certificate-file.p12
    certificate-password = password
    certificate-alias = friendly-name
Real User Monitoring (JavaScript)
  • Angular 8 will be released soon and is supported by OneAgent 1.165.
Synthetic Monitoring
  • Synthetic HTTP monitoring is now possible from Windows-based ActiveGates. Simply install a synthetic-enabled Windows ActiveGate and add it to a synthetic monitoring location to start HTTP synthetic monitoring.
Other changes
For important bug fixes and other changes, as well as previous release notes, see the release changelog.
The post OneAgent & ActiveGate release notes, version 1.165 appeared first on Dynatrace blog.