Beginning in February 2020, AppDynamics switched from Semantic Versioning to Calendar Versioning for some agents and the first deployments of SaaS Controllers. In March 2020, the entire product suite will use Calendar Versioning.

Skip to end of metadata
Go to start of metadata

Related pages:

Your Rating:
1 Star2 Star3 Star4 Star5 Star
3 rates
The following notes describe 4.5.x updates to the .NET Agent.

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 (

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

4.5.19 Updates

Version 4.5.19 - January 28, 2020


The .NET Agent for Linux now:

  • Automatically detects Critical and Error level exceptions for ILogger interfaces. The agent collects error details for exceptions and log messages.   
  • Supports end-to-end monitoring of transactions that use RabbitMQ.
  • Provides limited callgraph visibility in performance snapshots in .NET Core 2.x. The agent collects timing information for backend calls only.  Due to limitations of .NET Core CLR 2.x, complete call stack timing information is not available. Updates

Version - December 20, 2019

  • You can now monitor Azure Functions version 1.x with the .NET Agent.  
  • The .NET Agent for Linux now logs thread IDs to improve troubleshooting.
  • The .NET Agent for Windows now automatically detects Azure Service Bus backends and provides out of the box correlation for Service Bus on Azure Functions. 

4.5.18 (.NET Agent for Windows) Updates 

Version 4.5.18 - December 18, 2019

End of Life Notice
  • The .NET Agent no longer supports out of the box correlation with IBM Websphere MQ. 

4.5.17 Updates

Version 4.5.17 - November 22, 2019

  • The .NET Agent now supports .NET Core 3.0 on Windows. 
  • The .NET Agent for Linux now detects and monitors calls to an Oracle database.

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. Learn more. 
  • The .NET Agent now supports .NET Core 3.0 on Linux, including code-level callgraphs in snapshots. Learn more. 

4.5.15 Updates

Version 4.5.15 – October 1, 2019


  • The .NET Agent for Linux now can now report metrics for .NET application calls to MongoDB backends
  • AppDynamics now supports Network Visibility for .NET applications running on Windows. This feature is not enabled by default. See the socket-enabled property for information on enabling this feature. For information on supported frameworks, see Network Visibility Requirements and Supported Environments.

Resolved Issues

DOTNET-540Include host and app pool name in events reported for uninstrumented processes.
DOTNET-3991Passwords are not removed from the database connection string if the string includes a white space.
DOTNET-4044The .NET Agent for Linux versions 4.5.13 and 4.5.14 process crashes when APPDYNAMICS_PREVIEW_FEATURE_ENABLED is set to true and application monitoring preview features such as custom business transactions or backend naming are implemented.
DOTNET-4066A null reference exception occurs with .NET Agent versions 4.5.13 and 4.5.14 where instrumentation of the agent incorporates setting full-no-dependency to false.

4.5.14 Updates

Version 4.5.14 – August 28, 2019

Resolved Issues

DOTNET-4075NETVizExitNotificationHandler null reference exception in agent logs when Network Visibility is disabled
DOTNET-4069Analytics error transactions are logged to the agent continually when Analytics is enabled in the Controller but the Analytics Agent is not running on the app server
DOTNET-3890Agent is reporting incorrect agent type in agent logs
DOTNET-3442Agent causing high thread count on instrumented applications in rare scenarios

4.5.13 Updates

Version 4.5.13 – July 25, 2019


  • This release brings the .NET Agent for Linux closer to parity with the .NET Agent for Windows by providing a feature preview for HTTP backend detection and naming using Custom HTTP Discovery Rules. Configure the .NET Agent for Linux to detect HTTP backends using URI segments, instead of detecting and naming the backend using the default autodiscovery rules that identify the backend based solely on the Host and Port. Using Custom HTTP Discovery rules is especially useful to detect and name HTTP backends behind an API gateway or portal. Defining the HTTP backend based on the URL segments in the Custom HTTP Discovery rule enables AppDynamics to resolve the HTTP backends to tiers properly, giving you accurate metrics for your API services. See HTTP Backend Detection and .NET Backend Detection

    There is a known issue in HTTP backend detection configuration in the current preview. When defining HTTP backend using URL segments, segment enumeration starts with number 2 instead of number 1, and segment 1 always returns empty. For example, to define unique backends using the first two segments of the URL, you would need to configure HTTP backend detection to use the first 3 segments or segment 2 and 3.
  • The .NET Agent for Linux now collects and displays error metrics for exceptions handled using either the ASP.NET Core exception handler page or exception handler lambda.

Resolved Issues

DOTNET-3911NET Core Linux crashes with ‘invalid pointer' exception
DOTNET-3816 MIDC causing AD_STACK_TRACE:System.InvalidProgramException
DOTNET-3785Applications written using AutoMapper and instrumented with the .NET Agent for Linux may crash. Microsoft implemented a fix for this problem in the .NET Core CLR. Please upgrade to CoreCLR versions 2.1.12 or 2.2.6.

4.5.12 Updates

Version 4.5.12 – June 20, 2019

Resolved Issues

DOTNET-3401Provide support for MongoDB2.7/2.8 for .NET Agent for Windows.

Fix .NET Agent for Windows Agent errors resulting in overhead while monitoring apps using MongoDB Driver 2.7 on Windows. Full support of MongoDB driver version 2.7 will follow at a later date.

4.5.11 Updates

Version 4.5.11 – May 16, 2019


The .NET Agent and .NET SDK for Linux now support proxy access to the Controller. You can configure the proxy in the AppDynamicsConfig.json file or by defining the relevant environment variables. See .NET Agent for Linux Environment Variables.NET Agent for Linux Advanced Configuration Options, and Using .NET Core for Linux SDK.

Resolved Issues

DOTNET-3485POCO business transactions are not identified in Azure Service Fabric app

4.5.10 Updates

Version 4.5.10 – April 22, 2019


Resolved Issues

DOTNET-3596.NET Microservices Agent may cause exception for applications using SQL Reporting Services Report Viewer control.

4.5.9 Updates

Version 4.5.9 – March 29, 2019


  • Edging towards the goal of parity with the .NET Agent for Windows, in this release, the .NET Agent for Linux provides improvements to business transaction detection, configuration, and naming. In the Controller UI you can limit the transactions monitored by choosing to include or exclude ASP.NET and POCO business transactions matching criteria you specify. See .NET Agent Business Transaction Configuration
    The ability to customize Business Transaction detection that is now supported by .NET Agent for Linux version 4.5.9 requires Controller versions 4.5.2 and higher. The .NET Agent for Linux version 4.5.9 works with Controller version 4.4.1 and higher, but the customizable transaction detection and configuration capabilities require 4.5.2 and later versions of the Controller. See Agent and Controller Compatibility.

 For Controller versions 4.4.2 to 4.5.1 and the .NET Agent for Linux, AppDynamics defaults to use two segments for ASP.NET business transaction naming. 

Resolved Issues
DOTNET-3675Windows service application is crashing with AppDynamics NLog call stack.

4.5.8 Updates

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. 
Resolved Issues
DOTNET3224Identify REDIS backends using host name rather than server name, as server name changes frequently. Prevents backend explosion
DOTNET3436Slow memory leak affecting Full and Microservice .NET Agents
DOTNET-3561Runtime Reinstrumentation Handle Leak
DOTNET3574.NET Microservice Agent for Linux causes application exception when Analytics is enabled

4.5.7 Updates

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.
Resolved Issues
DOTNET-3416JDBCConfiguration.isAnalyticsCPMLimitReached throws NullReferenceException
DOTNET-3420Snapshot URLs are missing for regular Asp.Net type BTs
DOTNET-3505EXC_BAD_ACCESS in AppAgent::stopExitCall

4.5.6 Updates

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.

4.5.5 Updates

Version – November 29, 2018

Resolved Issues
DOTNET-2767Sitecore app crashes with an access violation when the agent is instrumenting the app
DOTNET-3055Ability to use APPDYNAMICS_AGENT_NODE_NAME in Web.config for multiple .Net Core apps using same NodeID
DOTNET-3206Coordinator service cannot start after installation
DOTNET-3277Installation fails on Windows 2012 R2 64-bit
DOTNET-3298Failed to create interceptor for: Azure Service Fabric Exit v2

4.5.4 Updates

Version – October 25, 2018

Resolved Issues
DOTNET-2835Synchronization bug in ADConcurrentLinkedQueue can cause exception
DOTNET-3201When the .NET Agent MSI is not signed correctly, errors are thrown from Windows Smartscreen

4.5.2 Updates

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

Resolved Issues
DOTNET-2725Exceptions in Orleans tier not reported by agent monitoring Orleans app
DOTNET-2787SSRS crash due to agent-bootstrap-instrumentations
DOTNET-2790Missing Microsoft Azure search exit calls
DOTNET-2868Custom instrumentation for Azure webjob is not working
DOTNET-3140Add Package "AppDynamics.AgentSDK --version 4.5.1" with .NET Core SDK 2.1.x is failing the assembly reference

4.5.1 Updates

Version – August 29, 2018 

  • The .NET Agent now supports .NET Core 2.0 and 2.1
Resolved Issues
DOTNET‑2703Special characters in custom name causes System.Runtime.InteropServices.SEHException in Profiler Log
DOTNET-2764Incorrect async transaction boundary for POCO returning Task
DOTNET-2768Service endpoints are not instrumenting with microservices/standalone agent
DOTNET-3006Azure site extension missing

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.
Resolved Issues
DOTNET-1351Machine snapshots do not show CPU percentage and process when ProcessNameFormat is set to 2
DOTNET-1319Agent is not able to identify the ADO.NET exit for the System.Data.Common.DbDataAdapter class methods
DOTNET-2420QueueTask intermittent instrumentation issue when ReJIT is enabled
DOTNET‑2425Missing HTTP Exit calls result in inconsistent correlation with downstream tiers
DOTNET-2443Auto node naming is not working in Service Fabric cluster for .NET Core
DOTNET-2490Cache-Control value is modified when EUM BT correlation is enabled
DOTNET-2575.NET Core SDK 2.1.300 triggers BadImageFormatException