OneAgent and ActiveGate changelog version 1.163

Blog post

Resolved issues

General Availability (Build .163)

The .163 GA release contains 56 resolved issues.

Agent & SG

  • CloudFoundryInfo and CloudFoundryAppInstance should be sent on Windows DiegoCells. (APM-160161)

Agent Installer

  • Command-line interface of oneagentctl was improved. (APM-152427)
  • OneAgent Linux installer will now deploy SELinux module on Red Hat CoreOS. (APM-161936)
  • Improved messages displayed by AIX installer when Cloud-infrastructure monitoring mode is enabled. (APM-156982)
  • FIXED misleading errors printed to healthcheck.log when OneAgent is deployed as a container. (APM-161873)

Core

  • In rare circumstances the container injection may suspend startup of containers. (ONE-22353)
  • Fixed injection into certain musl-libc based containers in CloudFoundry environments. (ONE-22357)
  • Fixed bug that prevented process startup on AIX for processes that do not have a fully populated /proc filesystem entry. (ONE-21740)
  • Fixed injection into windows docker containers with non-default data root directory. (ONE-22359)
  • Resolved incompatibility with runc security fix CVE-2019-5736, which prevented container injection. (ONE-22324)
  • Linux disk IO metrics are now supported when device name is a link (e.g. LVM Partitions). (ONE-21462)

Java

  • OneAgent 1.159.223 crashing IBM JVMs. (ONE-21668)
  • Custom JavaScript library path / beacon path not considered by java agent when instrumented proxy is in place. (ONE-21116)

.NET

  • Subsequent asynchronous calls were not captured after an asynchronous HTTP request from the HttpClient class. (ONE-22448)
  • Asynchronous custom services called in a loop created a recursive service flow. (ONE-21840)
  • HTTP Tagging Sensor may cause a NullReferenceException in HttpClient.SendAsync method, when a custom implementation of HttpRequestMessage is used. (ONE-22164)

NodeJS

  • RabbitMQ sensor: improve temporary queue detection mechanism in order to prevent potential queue-instance explosion. (ONE-21778)
  • Agent injection improvement: No agent was injected if a folder with same name as a script file was present. (ONE-21199)
  • Inject Node.js Agent into preloaded scripts (-r option). (ONE-20935)
  • Fix potentially excessive startup overhead in gRPC sensor. (ONE-20858)
  • Improved logging of request attributes not put on a node. (ONE-21527)
  • Node.js AutoSensor could not be disabled via "Deep monitoring / Troubleshooting" settings UI. (ONE-21659)

PHP

  • URI filtering for SOAPSensor and StreamSensor. (ONE-20570)
  • Fix for not recognized DT environment variables.Now they are checked just after reading php.ini. (ONE-21306)
  • Segmentation fault in Apache. (APM-160845)

Go

  • GoLang agent may cause a crash of "OpenShift" process. (ONE-21258)
  • Class browser failed to send requested data (as required for defining custom services). (ONE-21775)
  • Agent was not fully functional when it was inactive on startup but returned to active some time later. (ONE-21663)
  • "Background CPU method hotspot information" did no longer provide data, once the (internal) node limit was reached. (ONE-21773)
  • "Background CPU method hotspot information" was not available, when Agent was inactive on startup but returned to active some time later. (ONE-21825)
  • Agent failed to shutdown when Go died with runtime.dieFromSignal(). (ONE-21874)

JavaScript

  • Added a JavaScript API sample to mark a page as failed. (ONE-18558)
  • Added a JavaScript API sample to mark an XHR action as failed. (ONE-18557)
  • Added information about the last modification before the page was visually complete. (ONE-13250)
  • Added a workaround for an IE Bug that shows a modal dialog, if navigator.cookieEnabled was called via javascript in a modal dialog. (ONE-19910)
  • Added a flag to resources to show which resources were considered for the Visually Complete metric. (ONE-14235)
  • Empty pages would sometimes report load actions that end before their onload subaction on Internet Explorer. (ONE-20702)
  • Improved performance of resource timing calculation. (APM-158370)
  • If both support for failed images and support for XHR mutations are enabled, the action duration doesn't take account of any mutations . (ONE-22046)
  • Resource timing duration is 0 for all resources on Safari 12. (ONE-22074)

OS Agent

  • OS Agent should copy IISAgentConfigSchema.xml to IIS config directory. (APM-159465)
  • implement TimestampConverter on AIX and verify if Restart Required is working. (APM-135001)
  • IBM Java 1.4 version detection has been added. (APM-154081)
  • Enable InProcStore reading in OsAgent for AIX. (APM-157075)
  • KVM Virtual Machines will now be discovered on PPCLE. (APM-158909)
  • Detection of listen ports for IIS has been improved, to not occasionally have misassignments due to network traffic based heuristic. (APM-164314)
  • Fixed incorrect injection status for PGI consisting of both Java and GO processes. (APM-164947)
  • Executable name will be used for identification of processes, in scenarios where OSAgent cannot resolve /proc/<pid>/exe symlink. (APM-165820)
  • Detection of virtual network interfaces on Azure has been enhanced. (APM-162488)
  • OSAgent will no longer attempt to discover version of Kubernetes processes running inside containers. (APM-162996)
  • Cloud Foundry discovery heuristic has been updated to support version 2.4. (APM-166244)

Network Agent

  • Libpcap has been updated to allow monitoring of interfaces on Kernels without the https://github.com/torvalds/linux/commit/474ff2600889e16280dbc6ada8bfecb216169a70 fix. (APM-152202)
  • Windows network adapters with Unicode descriptions should now be properly detected. (APM-161859)

Logging Agent

  • Fixed downloading log files without timestamps. (APM-159197)
  • Proper offset calculation for log lines. (APM-163253)

IIB

  • OS agent support for IIB11 (IBM App Connect). (ONE-20430)

Early Adopter releases

The following Early Adopter releases are in progress starting with this OneAgent release.

Dynatrace OneAgent can now deep monitor message flows running on the IBM Integration Bus

Factsheet
Enable
IBM Integration Bus support can be enabled with the Dynatrace Settings > Monitoring > Monitored technologies > IBM Integration Bus switch.
Planned GA date
Not yet confirmed