AppDynamics switched from Semantic Versioning to Calendar Versioning starting in February 2020 for some agents and March 2020 for the entire product suite.


    Skip to end of metadata
    Go to start of metadata

    Related pages:

    Your Rating:
    Results:
    1 Star2 Star3 Star4 Star5 Star
    18 rates

    Supported Runtime Environments

    This section lists the environments where the .NET Agent does some automatic discovery after little or no configuration.

    OS Versions

    • Microsoft Windows Server 2008 (32-bit and 64-bit)
    • Microsoft Windows Server 2008 R2
    • Microsoft Windows Server 2012
    • Microsoft Windows Server 2012 R2
    • Microsoft Windows Server 2016
    • Microsoft Windows 7, 8, 8.1, 10

    Microsoft .NET Frameworks

    Microsoft .NET Framework versions 2.0, 3.0, 3.5, 4.0, 4.5, 4.5.2, 4.6, 4.7 on the following runtime environments:

    • Microsoft IIS versions 6.0, 7.0, 7.5, 8.0, 8.5, 10
    • Managed Windows Services
    • Managed Standalone Applications
    • Microsoft SharePoint 2010, 2013 as services running inside IIS
    • Microsoft ASP.NET Core 2.0/2.1 for Windows
    • Microsoft ASP.NET Core 2.2 for Windows is supported for .NET Agent versions 4.5.7 and later
    • Microsoft ASP.NET Core 3.1 for Windows is supported for .NET Agent versions 20.3 and later

    Microsoft Windows Azure

    • Azure App Services for .NET 4.6 environments in the Azure Portal
      • Web Apps
      • Web Jobs
      • API Apps
      • Container Services
      For Azure App Services, the .NET Machine Agent disables certain .NET Machine Agent infrastructure monitoring features: CLR crash reporting, machine snapshots, and Windows performance counter monitoring.
    • Azure Cloud Services
      • Web Roles
      • Worker Roles

    Unsupported Frameworks

    • Microsoft .NET versions 1.0, 1.1
    • Unmanaged native code

    Automatically Discovered Business Transactions

    The .NET Agent discovers business transactions for the following frameworks by default. The agent enables detection without additional configuration.

    Type

    Custom Configuration Options?

    Downstream Correlation?

    ASP.NET*

    Yes

    Yes

    ASP.NET MVC 2
    ASP.NET MVC 3
    ASP.NET MVC 4
    ASP.NET MVC 5

    Yes

    Yes

    ASP.NET Core on the full frameworkYesYes

    Open Web Interface for .NET (OWIN) web API

    YesYes

    .NET Remoting

    No

    See Enable Correlation for .NET Remoting.

    Windows Communication Foundation (WCF)

    No

    Yes

    Web Services including SOAP

    No

    Yes

    Message Queues



    Apache ActiveMQ NMS framework and related MQs

    No

    Yes

    IBM WebSphere MQ

    No

    Yes

    Microsoft Message Queuing (MSMQ)NoYes
    Microsoft Service Bus / Windows Azure Service BusNoYes
    NServiceBus over MSMQ or RabbitMQ transportNoYes
    RabbitMQYesYes

    TIBCO Enterprise Message Service

    No

    Yes

    TIBCO Rendezvous

    No

    Yes

    Windows Azure QueueNoNo

    The .NET Agent automatically discovers entry points for ASP.NET web forms with the Async property set to "true" in the Page directive.

    Supported Loggers for the .NET Agent

    • Log4Net
    • NLog
    • System Trace
    • Windows Event Log

    If you are using a different logger, see Error Detection.

    Remote Service Detection

    The .NET Agent automatically detects the following remote service types. The agent enables detection by default. You do not need to perform extra configuration.

    Type

    Custom Configuration Options?

    Async Detection?*

    Downstream Correlation?

    Directory Services, including LDAP

    No

    No

    N/A

    HTTP

    Yes

    See Asynchronous Exit Points for .NET.

    Yes

    MongoDB: C# and .NET MongoDB Driver version 1.10, 2.0NoSee Asynchronous Exit Points for .NET.N/A

    .NET Remoting

    Yes

    No

    See Enable Correlation for .NET Remoting.

    WCF

    Yes

    See Asynchronous Exit Points for .NET.

    Yes

    WCF Data Services

    Yes

    No

    No

    Web Services, including SOAP

    Yes

    See Asynchronous Exit Points for .NET.

    Yes

    Azure Service Fabric Remoting v1 and v2—for the .NET Microservices Agent---
    Data Integration


    Microsoft BizTalk Server 2010, 2013NoYesSee Correlation Over Microsoft BizTalk.

    Message Queues




    Apache ActiveMQ NMS framework and related MQs

    Yes

    No

    Yes

    IBM WebSphere MQ (IBM XMS)

    Yes

    No

    Yes

    Microsoft Message Queuing (MSMQ)

    Yes

    See MSMQ Backends for .NET

    See MSMQ Backends for .NET

    Microsoft Service Bus / Windows Azure Service Bus

    No

    Async exit points only

    Yes

    NServiceBus over MSMQ or RabbitMQ transportNoSee NServiceBus Backends for .NETYes
    RabbitMQSee RabbitMQ Backends for .NETNoYes

    TIBCO Enterprise Message Service

    Yes

    No

    Yes

    TIBCO Rendezvous

    Yes

    No

    Yes

    Windows Azure Queue

    No

    No

    No

    * The agent discovers asynchronous transactions for the Microsoft .NET 4.5 framework. See  Asynchronous Exit Points for .NET

    Supported Windows Azure Remote Services

    Type

    Customizable Configuration?

    Downstream Correlation?

    Azure Blob

    No

    No

    Azure Queue

    No

    No

    Microsoft Service Bus

    No

    Yes

    Cache Clients

    Type

    Customizable Configuration?

    Async Detection?*

    AppD for Databases?

    StackExchange.RedisNoYesNo


    Data Storage Detection

    The .NET Agent automatically detects the following data storage types. The agent enables detection by default. You do not need to perform extra configuration.

    Type

    Customizable Configuration?

    Async Detection?*

    AppD for Databases?

    ADO.NET (see supported clients below)

    Yes

    Yes

    No

    Windows Azure Blob Storage

    No

    Yes

    No

    Windows Azure File StorageNoYesNo
    Windows Azure Table StorageNoYesNo

    * The agent discovers asynchronous transactions for the Microsoft .NET 4.5 framework. See Asynchronous Exit Points for .NET

    Supported ADO.NET Clients

    AppDynamics can monitor any ADO.NET client version and type. Clients we've tested include the following:

    Database Name

    Database Version

    Client Type

    Oracle

    10, 11, 12

    ODP.NET

    Oracle

    10, 11, 12

    Microsoft Provider for Oracle

    MySQL

    5.x

    Connector/Net and ADO.NET

    Microsoft SQL Server*

    2005, 2008, 2012

    ADO.NET

    * Microsoft, SQL Server, and Windows are registered trademarks of Microsoft Corporation in the United States and other countries.