Dynatrace Agent release notes for version 1.75

Automatic Updates for Dynatrace Agent

The upgrade from version 1.73 to 1.75 and all further updates of Dynatrace Agent can now be done fully automatically. As soon as a new agent version is available the agent will download the new version and upgrade itself. Upgrading is fast enough so you typically do not lose any data. To make sure that also the server processes like Java, Apache, .NET, etc. are monitored with the latest technology, you will need to restart them. However, you can do that at your own convenience, the processes will still be monitored without a restart.

To enable or disable automatic updates, go to Settings and then Updates:

General performance improvements of our DB support

We’ve made a significant improvement to our DB support in all supported technologies, which can even make the impact of Dynatrace Agent (in extreme cases of many long SQLs strings) close to none.

Security Gateway improvements and fixes

Support for ESXi hosts with non-unique UUIDs

Note: making this work requires configuration changes. You need to create a file named esx_id_extended in the Security Gateway configuration directory. Restart Security Gateway afterwards.

The location of Security Gateway configuration directory is:

  • C:\ProgramData\ruxit\gateway\config (Windows)
  • /var/lib/ruxit/gateway/config (Linux)

GC support for Node.js

We are starting to add metrics around garbage collection and GC to our Node.js monitoring. Beginning with this version you can see the GC suspension metric on a Node.js process. We will extend this further to include CPU usage of GC and all heap metrics soon.

MongoDB support for Node.js

Starting with this version we report MongoDB interactions in Node.js. In the Dynatrace interface this looks very similar to how we already do this for Java as described in the Dynatrace blog.

.NET monitoring goes GA

The .NET monitoring is GA starting with version 1.75.

  • It automatically adds visibility into any IIS App pool based on .NET.
  • Users can manually enable visibility for standalone .NET processes by switching on monitoring for them in the Monitoring overview.
  • Existing customers need to manually enable global .NET support for App pools after they upgrade Dynatrace Agent to 1.75. If they do not want this they can control it on a per host basis.

Guido is a Director, Product Management at Dynatrace with a technical background in developing enterprise software and monitoring solutions. Guido looks after a wide range of Dynatrace technologies, from OneAgent to the UI. He's always looking for ways of improving product usability and simplifying the complexities of APM.