Download PDF
Download page .NET Supported Environments.
.NET Supported Environments
Supported Runtime Environments
This section lists the environments where the .NET Agent does some automatic discovery after little or no configuration. See Browser RUM Supported Environments for additional supported environments.
Out-of-process IIS applications should be instrumented as standalone applications.
OS Versions
All versions of Windows (x86/x64) and Linux (x64) operating systems (OS) supported by the target runtime and operating system vendor.
Runtimes
AppDynamics only supports versions of .NET Framework that Microsoft currently supports. Previous versions not listed are not supported by Microsoft, or by AppDynamics. See Microsoft .NET Framework Supported Versions.
- Microsoft .NET Framework: 3.5 SP1, 4.6.2, 4.7.x, 4.8.x
Microsoft .NET: 6, 7
Hosts
- Managed Standalone Applications
- Managed Windows Services
- Microsoft IIS
- Microsoft SharePoint 2010, 2013 as services running inside IIS
Microsoft Windows Azure
- Azure App Services on Windows in the Azure Portal
- Web Apps
- Web Jobs
- API Apps
- Container Services
- Azure Cloud Services
- Web Roles
- Worker Roles
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 | Yes | Yes |
ASP.NET Core | Yes | Yes |
Open Web Interface for .NET (OWIN) web API | Yes | Yes |
.NET Remoting | No | |
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) | No | Yes |
Microsoft Service Bus / Windows Azure Service Bus | No | Yes |
NServiceBus over MSMQ or RabbitMQ transport | No | Yes |
RabbitMQ | Yes | Yes |
TIBCO Enterprise Message Service | No | Yes |
TIBCO Rendezvous | No | Yes |
Windows Azure Queue | No | No |
* 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
- Loggers on .NET Core that implement the Microsoft.Extensions.Logging.ILogger API
If you are using a different logger, see Error Detection.
Remote Service Detection
The .NET Agent automatically detects these 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? |
---|---|---|---|
CosmosDB:
| No | See Asynchronous Exit Points for .NET. | N/A |
Directory Services, including LDAP | No | No | N/A |
HTTP | Yes | Yes | |
MongoDB: C# and .NET MongoDB Driver version 1.10, 2.0 | No | See Asynchronous Exit Points for .NET. | N/A |
.NET Remoting | Yes | No | |
WCF | Yes | Yes | |
WCF Data Services | Yes | No | No |
Web Services, including SOAP | Yes | Yes | |
Azure Service Fabric Remoting v1 and v2—for the .NET Microservices Agent | - | - | - |
Data Integration | |||
Microsoft BizTalk Server 2010, 2013 | No | Yes | See 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 | ||
Microsoft Service Bus / Windows Azure Service Bus | No | Async exit points only | Yes |
NServiceBus over MSMQ or RabbitMQ transport | No | See NServiceBus Backends for .NET | Yes |
RabbitMQ | See RabbitMQ Backends for .NET | No | Yes |
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.Redis | No | Yes | No |
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 Storage | No | Yes | No |
Windows Azure Table Storage | No | Yes | No |
* 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.
Other Backends
- ADO.NET backend calls (SqlClient, MySql, SQLite, PostgreSQL)
- EntityFramework
.NET Agent Frameworks for OpenTelemetry
Vendor | Framework | Version(s) | Entry Points | Exit Points |
---|---|---|---|---|
Microsoft | ASP.NET Core | 6.0 | Yes | - |
Microsoft | Web Services (HttpClient) | 6.0 | - | Yes |
Limitations
- Tier network dashboard is not supported on .NET Core / .NET runtime.
- Node memory is not supported on Linux.
Cisco Secure Application does not support single file deployment.
- For .NET Framework, AppDynamics reports vulnerable assemblies. To see if an agent is reporting correctly, navigate to the Cisco Secure Application dashboard, go to Application, click the desired Tier, then click the desired Node name. After selecting the Node, you can view the Last Dependency Reported column.