Dynatrace Agent release notes for version 1.91


  • Ability to override the Virtual host of Web request services for local host scenarios.
    See How does Dynatrace detect and name services?#Webrequestservices
    Dynatrace uses the virtual host to name web request services. In some cases this is just localhost or if isn’t configured at all it defaults to the name of the actual host. This is not always desired and especially in docker and PaaS scenarios leads to many localhost services, or worse new services all the time, when instances get restarted (new hostname). Users can now use the an environment variable to define a Virtual Host name for these localhost scenarios.
    Simply set RUXIT_LOCALTOVIRTUALHOSTNAME to any value, e.g. www.ruxit.com and Dynatrace will pick it up to replace localhost virtual host names with it.
  • Ability to exclude dynamic ports from service detection.
    See How does Dynatrace detect and name services?#Webrequestservices
    Dynatrace takes the listen port of a web request service into account when naming and detecting it. In some cases these ports are meaningless and dynamic (change after restart). This is especially true if there exists a load balancer that dynamically assigns ports to the application process. You can now set an environment variable RUXIT_IGNOREDYNAMICPORT=true. This will remove the port from the detection and replace it with *.


  • Adding Code-level hotspots for Nginx web server (module response time contribution)

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.