OneAgent & Security Gateway release notes v1.149

OneAgent

Java

  • We’re proud to announce the new public beta for Akka remoting as a deep code-analysis module for Java monitoring in Dynatrace (requires Dynatrace SaaS version 1.152).
  • It’s now possible to access fields in Java objects. Read more about the new functionality in this article about Deep Object Access.

.NET

  • Announcing the new public beta for end-to-end request tracing across RabbitMQ queues for .NET. Dynatrace already supports this for Java and Node.js (requires Dynatrace SaaS version 1.152).

Go

  • We’ve performed a full de-support of Go versions 1.5 and 1.6. While these versions were never officially supported, they were known to work. OneAgent no longer monitors these Go versions.

General improvements & fixes

  • We’re excited and proud to announce the public beta release of Docker for Windows (Windows Server Containers). For more information about this release, available features, and known limitations, see the Docker for Windows announcement.
  • Several months ago we announced the public beta release of full-stack OneAgent for the AIX operating system. Since then, we’ve collected valuable feedback from our customers, for which we’re grateful. One of the requested features is to enhance the monitoring of CPUs for LPARs (Logical Partitions) with information about entitlement and its consumption. With OneAgent version 1.149, we now offer a new graph that shows the entitlement, physical CPU consumption over time, and the percentage of entitlement used. Hopefully, this will make AIX resource allocation planning easier in cases of detected performance degradation. We’re continuing work on other AIX monitoring enhancements, so stay tuned for more updates.
    OneAgent v1.149
  • We’re continuing the improvements of OneAgent installation on Windows. This is part of the larger re-architecting of the OneAgent installation package. Further enhancements are coming.
  • The OneAgent installer for AIX now performs a system and version compatibility check. If the version of AIX doesn’t meet the support criteria, the installation aborts. For details on all supported AIX versions, see our Supported technologies page.
  • The Linux full-stack OneAgent installer now verifies global readability of the /var/lib/dynatrace/oneagent directory as part of its system check routine.
  • The infrastructure and network monitoring modules of OneAgent perform additional checks of system capabilities required for non-root mode. To find out more about non-root mode for OneAgent for Linux, please see our earlier blog post announcing the public beta phase of non-root mode.
  • Dynatrace Help is updated each week with new documentation and enhancements to existing Help topics. You can now track the updates we’re making to Dynatrace Help by visiting the What’s new in Dynatrace Help? page. This page is updated weekly with all significant updates to Dynatrace Help, so check back often.

Cloud platform support

  • If you’ve enabled Cloud Foundry full-stack monitoring via the Dynatrace OneAgent BOSH add-on, OneAgent now also detects additional BOSH instance metadata. You’ll now find BOSH instance ID, BOSH instance name, BOSH availability zone, and BOSH deployment ID as part of the host properties of each of your BOSH-managed Cloud Foundry VMs.
  • We’ve also improved the auto-detected host name of BOSH-managed VMs. Due to the needs in large Cloud Foundry environments, the auto-detected host name of BOSH-managed VMs has been changed from BOSH instance name/index to BOSH instancename/BOSH instance ID.
  • Process group detection rules are now also available for PaaS integrations (for example, for all Cloud Foundry build pack integrations or Kubernetes and OpenShift application-only monitored applications).
  • Added support for Kubernetes 1.10.x and 1.11.x
  • Kubernetes versions <= 1.6 are no longer actively maintained by the Kubernetes community. We’ll de-support Kubernetes version 1.6.x and lower with OneAgent version 1.153.
  • Dynatrace OneAgent Operator release version 0.1.0 is out. For details, see OneAgent Operator release for your K8S and OpenShift environments.
  • Using Dynatrace OneAgent Operator is the recommended approach to monitoring Kubernetes 1.9+ and Openshift 3.9+.
  • OneAgent in Google Cloud Platform reports important metadata for Google Compute Engine instances. GCE zone, GCE Instance id, GCE Instance name, and GCE Machine Type are now reported along with other host properties.
  • The Heroku buildpack for Dynatrace OneAgent now also supports improved OneAgent error handling via the SKIP_ERRORS configuration option. This option allows for the successful push of your application even when download of Dynatrace OneAgent fails (for example, because of a network connection error).

Important bug fixes

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

  • APM-132248 – Windows installer of OneAgent was found to fail to preserve the configuration during the auto update in some obscure cases.
  • APM-132579 – OneAgent installation on Windows was producing incorrect error messages when invoked again on a host where OneAgent was already deployed.
  • APM-132767 – In some cases (dependent on AIX system configuration) OneAgent installation was failing on AIX when alternative deployment path was specified.
  • APM-133514 – We have found that in some of the customers’ systems the cat command is not producing expected results (as strange as it may sound). This caused a failure in the process detection and injection module of OneAgent.
  • APM-133850 – AIX uninstallation was not clean in cases where OneAgent was working for extended period of time.
  • APM-131139 – hostautotag.conf file used for configuring tags for hosts was re-read completely regardless of the last modification date. This was changed to check for modification time stamp before the contents are re-read.
  • APM-131368 – There was a bug in AIX full-stack OneAgent which caused some processes to be reported with incorrect CPU usage.
  • APM-131379 – OneAgent was not properly detecting the version for nsolid binaries.
  • APM-129331 – OneAgent could not detect the network interfaces for network data collection, which resulted in no network metrics on the reports.
  • APM-132928 – One of OneAgent modules on AIX was creating multiple non-operational instances of itself.
  • APM-117969 – Security Gateway was trying to continue sending data to the cluster even though it has received an HTTP 410 response.

Upcoming beta releases

Stay tuned for the upcoming beta release of OpenStack infrastructure monitoring. We’re now in the final phase of testing. We’re very excited to be able to share these improvements with you soon.

Stay updated