If an artifact has been updated, the version number of the updated artifact and its availability date are listed below. The version number corresponds to that shown on the download portal (http://download.appdynamics.com).

The most recent releases appear at the top of the page.

4.5.8 Updates

Version 4.5.8.0 – February 22, 2019

Enhancements

You can analyze data collected from the .NET Agent for Linux, and create business monitoring dashboards to better understand your .NET Core applications with Transaction Analytics.

AppDynamics now automatically detects and monitors backend calls to Redis using the stackexchange library on .NET Core for Linux.

The .NET Agent supports IIS in-process hosting for ASP.NET Core 2.2. This enables you to monitor your .NET Core applications running on the latest .NET Core release, whether they are running in Azure or on-premise.

Resolved Issues

Key

Summary

DOTNET‑3224

Identify REDIS backends using host name rather than server name, as server name changes frequently. Prevents backend explosion

4.5.7 Updates

Version 4.5.7.0 – January 29, 2019

Enhancements

AppDynamics .NET Agent for Linux allows you to monitor your performance of .NET Core applications in production running on Linux OS, so you get real-time visibility of application performance, business transactions and resource metrics. The .NET Agent for Linux is available on AppDynamics Controller version 4.4.1+. The supported environments are constantly being updated. See .NET Agent for Linux for more information.

4.5.6 Updates

Version 4.5.6.0 – December 20, 2018

Enhancements

Controller and Agent environment variables now follow the standard underscore naming format. There are also two new variables APPDYNAMICS_CONTROLLER_SSL_CERTFILE and APPDYNAMICS_CONTROLLER_SSL_CERTDIR. See .Net Agent Configuration Properties for more information.

The .NET Agent supports functionality to reference any environment variables when configuringAgent Node Name, Agent Tier Name, or Controller Application Name.This should help when deployment slots are enabled in Azure App Services. You can monitor and analyze performance metrics from different deployment slots by using node names. See .NET Agent Environment Variables for more information.

4.5.5 Updates

Version 4.5.5.0 – November 29, 2018

Resolved Issues

Key

Summary

DOTNET-2767

Sitecore app crashes with Access violation when agent is instrumenting the app

DOTNET-3055

Ability to use APPDYNAMICS_AGENT_NODE_NAME in Web.config for multiple .Net core Apps using same NodeID

DOTNET-3206

Coordinator service cannot start after installation

DOTNET-3277

Installation fails on Windows 2012 R2 64 bit

DOTNET-3298

Failed to create interceptor for: Azure Service Fabric Exit v2

4.5.4 Updates

Version 4.5.4.0 – October 25, 2018

Resolved Issues

Key

Summary

DOTNET-2835

Synchronization bug in ADConcurrentLinkedQueue can cause exception

DOTNET-3201

When the .NET Agent MSI is not signed correctly, errors are thrown from Windows Smartscreen

4.5.2 Updates

Version 4.5.2.2717 – September 27, 2018

Enhancements

You can customize transaction correlation to enable AppDynamics transaction tracing where it would otherwise be unavailable for the .NET Core Microservices Agent. For example, you can extend transaction tracing across tiers spanning various services. See Configure Custom Correlation for .NET Applications for more information on custom correlation and how to configure it.