- Support for LinkerD 1.x
- We’ve introduced a more detailed split of memory metrics for monitored hosts. For more details about this change, see our improved host memory metrics blog post.
- For processes run under
chroot, there’s been high risk that deep code-monitoring module injection will fail and it then won’t be possible for collected data to be transferred outside of the injected technology. Such situations are now properly supported and a warning message is displayed when a monitored process is detected to be running under
- OneAgent now better handles the memory dump creation process and doesn’t raise unnecessary alerts.
- The process of generating host identifiers (so called
OSIIDs) is now improved to better handle virtual interfaces and cloud environments. This prevents the same
OSIIDfrom being created for different hosts and thus prevents data collisions.
- When OneAgent is deployed as a container in cases where a custom storage location is used, the installation path may point to a file system that is mounted as
noexec(which breaks OneAgent startup and installation) or
nosuid(which breaks non-privileged mode). We now support such situations by checking if installation paths are mounted as
nosuidand, if so, disallow installation.
- We’ve improved the URL checking mechanism in cases of OneAgent Docker image download, which might otherwise cause unnecessary warnings to be written to the log.
- We’ve reworked the activation of interfaces for packet capture on Linux. In case
libpcapis unable to find a continuous block in kernel address space,
ioctlis used to pass captured traffic to OneAgent. This eliminates most
page allocation failurekernel messages on systems where continuous blocks of memory are difficult to allocate.
- VLAN interfaces, including the basic statistics, are now reported on when the underlying physical interfaces aren’t set up with the IP addresses. This change doesn’t mean that we fully support VLAN interface monitoring (across all possible configurations), but it’s a step towards such support and we hope you find this to be a welcome improvement.
- We’ve also committed multiple other changes to OneAgent, improving its overall stability, resilience, as well as its monitoring and deployment automation.
OneAgent support changes
Dynatrace OneAgent support for the following platforms and components will be discontinued within the next 6 months:
- 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
- A new version of Azure Site-Extension for monitoring App Services is now available and features the following enhancements:
- Dynatrace fully supports vanilla Kubernetes 1.13 clusters with underlying Docker container runtime. CRI-O support will be introduced in the next releases.
- We’ve introduced a new Container monitoring settings page at Settings > Processes and containers to control injection into Docker, Garden, BOSH bpm, and Docker for Windows containers.
- OneAgent injection into BOSH bpm containers can be controlled via the container monitoring settings page. Injection into BOSH bpm is currently in Beta and the default state is set to
Off. Enable this setting if you’d like to get insights into Cloud Foundry platform processes.
- OneAgent now reports auto-update suppression reasons in cases where it’s deployed as a container and when underlying container runtime technology is different from Docker.
- OneAgent now reports additional GCE metadata for GAE and GKE.
- We’ve improved the detection of technologies like Cloud Foundry, Kubernetes, OpenShift, Istio, Linkerd, Etcd, and Go. For example, you’ll now find your Cloud Foundry platform processes in a dedicated Cloud Foundry category on the Technology overview page. We’ve also merged Gorouters and Auctioneers into this new category.
- OneAgent now reports the Kubernetes version in the Host properties section of each host overview page.
- We’ve extended the Early Access Program (EAP) for monitoring additional AWS services with EC2 SpotFleet, S3, Route 53, Kinesis Data Streams, and Firehose.
- The latest release of the Cloud Foundry Node.js buildpack v1.6.39 now uses our newly introduced common library for Go-based Cloud Foundry buildpacks.
- It’s now possible to create Management zones based on Cloud Foundry foundations.
For important bug fixes and other changes, as well as previous release notes, see the release change log.