Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: 4.5.16 agent release notes


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

4.5.16 Updates

Version 4.5.16 - October 28, 2019

  • You can now monitor Microsoft Azure Functions version 2.x hosted on the AppService plan with the .NET Agent. Install the AppDynamics Azure Site Extension and start collecting data from your Azure Functions.
  • The .NET Agent now supports .NET Core 3.0 on Linux, including code-level callgraphs in snapshots.

4.5.15 Updates

Version 4.5.15 - October 1, 2019


Version – February 22, 2019

  • 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. 


Version – January 29, 2019

  • 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.


Version – December 20, 2018

  • 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 configuring Agent 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.


Version – September 27, 2018

  • 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.

  • Service Fabric Support for the .NET Microservices Agent:

    • Service Fabric Remoting v.1 - full

    • Service Fabric Remoting v.2:
      Actors - full
      Stateful/Stateless services - OperationContract/ServiceContract name detection not available yet
      Tested on Microsoft.ServiceFabric.Services 3.1.274


Version – August 29, 2018 

  • The .NET Agent now supports .NET Core 2.0 and 2.1


4.5.0 Updates

July 11, 2018

  • .NET Core for Linux SDK
  • You can now include or exclude applications using the AppDynamicsConfig.json file.
  • Added new app agent node property queue-single-threaded. This property specifies the threading architecture for the IBM MQ message queue. The value defaults to "false."
  • AppDynamics integration with Pivotal Cloud Foundry (PCF) allows you to deploy AppDynamics-monitored .NET applications on the Pivotal platform. See .NET Application in PCF - Monitoring Workflow.