.NET agent: compatibility and requirements

New Relic's .NET agent supports both .NET Framework and .NET Core. This document describes compatibility and support for .NET runtimes, frameworks and libraries.

The agent includes built-in instrumentation for some of the most popular parts of the .NET ecosystem, including frameworks, databases, and message queuing systems. After you download and install the agent, it runs within the monitored process. The agent doesn't create a separate process or service.

For frameworks and libraries that aren't automatically instrumented, you can extend the agent with .NET custom instrumentation.

Want to try out our .NET agent? Create a New Relic account for free! No credit card required.

Requirements

Before you install the New Relic .NET agent on Windows or Linux, make sure your system meets these requirements:

The .NET agent is compatible with .NET Core version 3.1, and .NET 5.0, 6.0, 7.0, 8.0, and 9.0.

Important

The agent is only fully supported when instrumenting applications that target .NET runtimes currently supported by Microsoft. The agent is likely to work with the EOL'ed runtimes listed below, but we do not test new versions of the agent with EOL'ed runtimes.

.NET Core version	Minimum required .NET agent version
.NET Core 3.1 (EOL)	8.21.34.0 and higher
.NET 5.0 (EOL)	8.35.0 and higher
.NET 6.0 (EOL)	9.2.0 and higher
.NET 7.0 (EOL)	10.0.0 and higher
.NET 8.0	10.0.0 and higher
.NET 9.0	10.0.0 and higher

Important

On Linux ARM64 platforms, the .NET agent only supports versions of .NET 5.0 or higher.

The agent has been verified to work with the following operating systems:

Operating system	Supported versions
Windows (32- and 64-bit Intel compatible architectures)	Windows Server 2008 R2 SP1 Windows Server 2012 Windows Server 2012 R2 Windows Server 2016 Windows Server 2019 Windows Server 2022 Windows 10 Windows 11 Windows containers running on Server 2016 (NanoServer based images are not supported)
Linux (64-bit Intel compatible only)	All x64 Linux distributions supported by the .NET Core 2.0+/.NET 5+ runtime are supported by the .NET agent. For a full list, refer to Microsoft's documentation for the version of the runtime you are using.
Linux (ARM64/aarch64 architectures)	All ARM64 Linux distributions supported by the .NET 5+ runtime are supported by the .NET agent, with the following known exceptions: Alpine Linux

Operating system

Supported versions

Windows (32- and 64-bit Intel compatible architectures)

Windows Server 2008 R2 SP1
Windows Server 2012
Windows Server 2012 R2
Windows Server 2016
Windows Server 2019
Windows Server 2022
Windows 10
Windows 11
Windows containers running on Server 2016 (NanoServer based images are not supported)

Linux (64-bit Intel compatible only)

All x64 Linux distributions supported by the .NET Core 2.0+/.NET 5+ runtime are supported by the .NET agent. For a full list, refer to Microsoft's documentation for the version of the runtime you are using.

Linux (ARM64/aarch64 architectures)

All ARM64 Linux distributions supported by the .NET 5+ runtime are supported by the .NET agent, with the following known exceptions:

Alpine Linux

Installing and running the .NET agent requires these permissions:

Component	Necessary permissions
Install the agent	The process or user that installs the agent must have sufficient permissions to set environment variables and write access to the directory where the agent is installed.
Run the agent	The monitored process must have read/write access to the directory in which you installed the agent. The agent runs as a part of the monitored process and relies on those permissions to function. For applications using IIS via reverse proxy, the group `IIS_IUSRS` is often used.

Component

Necessary permissions

Install the agent

The process or user that installs the agent must have sufficient permissions to set environment variables and write access to the directory where the agent is installed.

Run the agent

The monitored process must have read/write access to the directory in which you installed the agent. The agent runs as a part of the monitored process and relies on those permissions to function.

For applications using IIS via reverse proxy, the group IIS_IUSRS is often used.

The .NET agent is compatible with applications targeting .NET Core 3.1, and .NET 5.0, 6.0, 7.0, 8.0, and 9.0. You can find the target framework in your .csproj file. Agent compatibility varies across different versions of .NET Core.

Compatible:

<TargetFramework>netcoreapp3.1</TargetFramework>

<TargetFramework>net5.0</TargetFramework>

<TargetFramework>net6.0</TargetFramework>

<TargetFramework>net7.0</TargetFramework>

<TargetFramework>net8.0</TargetFramework>

<TargetFramework>net9.0</TargetFramework>

Important

On Linux ARM64 platforms, the .NET agent only supports target frameworks of net5.0 or higher.

If you want to monitor an ASP.NET Core application targeting .NET Framework, ensure that you have enabled the .NET Framework support after installing the .NET agent.

Automatic instrumentation

If your application is hosted in ASP.NET Core, the agent automatically creates and instruments transactions. The .NET agent automatically instruments your application after install. If your app is not automatically instrumented, or if you want to add instrumentation, use custom instrumentation.

The .NET agent automatically instruments the performance of .NET application calls to these datastores:

Datastore	Instance details	Notes
Cosmos DB		The .NET agent `v9.2.0` or higher automatically instruments the Microsoft.Azure.Cosmos library. Minimum supported version: 3.17.0 Latest verified compatible version: 3.52.0 Versions 3.35.0 and higher are supported beginning with .NET agent v10.32.0
Couchbase		Use CouchbaseNetClient. Minimum supported version: 3.2.0 Latest verified compatible version: 3.6.6 Minimum agent version required: 10.40.0
Microsoft SQL Server		Use SqlClient from System.Data.SqlClient NuGet package or Microsoft.Data.SqlClient NuGet package. System.Data.SqlClient Minimum supported version: 4.4.0 Latest verified compatible version: 4.8.6 Microsoft.Data.SqlClient Minimum supported version: 1.0.19239.1 Latest verified compatible version: 6.0.2
Oracle		Use Oracle.ManagedDataAccess.Core Minimum supported version: 23.4.0 Latest verified compatible version: 23.9.0 Older versions of `Oracle.ManagedDataAccess.Core` may be instrumented, but have not been tested and are not supported.
PostgreSQL		Use Npgsql Minimum supported version: 4.0.0 Latest verified compatible version: 4.0.13 Prior versions of Npgsql may also be instrumented, but duplicate and/or missing metrics are possible.
MongoDB (modern driver)		Minimum supported version: 2.3.0 Latest verified compatible version: 3.3.0 Versions 3.0.0 and higher are supported beginning with .NET agent v10.40.0. Beginning in agent version 10.12.0, the following methods added in or after driver version 2.7 are instrumented: IMongoCollection.CountDocuments[Async] IMongoCollection.EstimatedDocumentCount[Async] IMongoCollection.AggregateToCollection[Async] IMongoDatabase.ListCollectionNames[Async] IMongoDatabase.Aggregate[Async] IMongoDatabase.AggregateToCollection[Async] IMongoDatabase.Watch[Async]
MySQL		Use MySql.Data or MySQL Connector MySql.Data Minimum supported version: 6.10.7 Latest verified compatible version: 9.3.0 MySqlConnector Minimum supported version: 1.0.1 Latest verified compatible version: 2.4.0
StackExchange.Redis		Minimum supported version: 1.0.488 Latest verified compatible version: 2.8.41
Elasticsearch		Use Elastic.Clients.Elasticsearch, NEST, or Elasticsearch.Net. Elastic.Clients.Elasticsearch Minimum supported version: 8.0.0 Maximum supported version: 8.15.10 Versions 8.10.0 and higher are supported beginning with .NET agent v10.20.1 Versions 8.12.1 and higher are supported beginning with .NET agent v10.23.0 NEST Minimum supported version: 7.0.0 Latest verified compatible version: 7.17.5 Elasticsearch.Net Minimum supported version: 7.0.0 Latest verified compatible version: 7.17.5
Memcached		Use EnyimMemcachedCore. Minimum supported version: 2.0.0 Latest verified compatible version: 3.4.0
DynamoDB		Use AWSSDK.DynamoDBv2. Minimum supported version: 3.5.0 Latest verified compatible version: 4.0.2 Minimum agent version required: 10.33.0
System.Data.ODBC		Use System.Data.Odbc. Minimum supported version: 8.0.0 Latest verified compatible version: 9.0.6 Minimum agent version required: 10.35.0 The following features supported for ODBC datastore calls in .NET Framework (using the built-in System.Data namespace) are not supported for .NET 8+: Connection `Open/OpenAsync` calls SqlDataReader `Read/NextResult` calls Slow SQL traces

The .NET agent does not directly monitor datastore processes. Also, the .NET SQL parameter capture in a query trace does not list parameters for a parameterized query or a stored procedure.

Collecting instance details for supported datastores is enabled by default. To request instance-level information from datastores not currently listed, get support at support.newrelic.com.

If your datastore isn't listed here, you can add custom instrumentation using the RecordDatastoreSegment method in the .NET agent API.

The .NET agent automatically instruments these external call libraries :

Libraries	Supported methods
HttpClient	The agent instruments these HttpClient methods: `SendAsync` `GetAsync` `PostAsync` `PutAsync` `DeleteAsync` `GetStringAsync` `GetStreamAsync` `GetByteArrayAsync`

Libraries

Supported methods

HttpClient

The agent instruments these HttpClient methods:

SendAsync
GetAsync
PostAsync
PutAsync
DeleteAsync
GetStringAsync
GetStreamAsync
GetByteArrayAsync

The .NET agent can be configured to automatically instrument these LLM frameworks:

Frameworks	Minimium framework version	Minimium agent version	Latest verified compatible version
AWS Bedrock	3.7.200.0	10.23.0 (`InvokeModelAsync`) 10.37.0 (`InvokeModelAsync`, `ConverseAsync`)	4.0.1
OpenAI	2.0.0	10.37.0 (`CompleteChat`, `CompleteChatAsync`)	2.1.0
Azure.AI.OpenAI	2.0.0	10.37.0 (`CompleteChat`, `CompleteChatAsync`)	2.1.0

The .NET agent can be configured to automatically instrument these logging frameworks for automatic logs-in-context with agent forwarding and local log decoration:

Frameworks	Minimium framework version	Minimium agent version	Latest verified compatible version
Log4Net	2.0.10	9.7.0	3.0.4
Serilog	2.5.0	9.7.0	4.3.0
NLog	4.5.0	9.7.0	6.0.1
Microsoft.Extensions.Logging	3.0.0	10.0.0	9.0.6

The agent automatically instruments these message systems:

Libraries	Supported methods
Confluent.Kafka	Produce and consume on topics. The following methods are instrumented: `IProducer.Produce` `IProducer.ProduceAsync` `IConsumer.Consume` Minimum supported version: 1.4.0 Latest verified compatible version: 2.10.1
NServiceBus	Puts and takes on messages. Minimum supported version: 5.0 Latest verified compatible version: 9.2.7
RabbitMQ	Puts and takes on messages and queue purge. When receiving messages using an `IBasicConsumer`, the `EventingBasicConsumer` is the only implementation that is instrumented by the .NET agent. `BasicGet` is instrumented, but the agent does not support distributed tracing for `BasicGet`. The following methods are instrumented: `IModel.BasicGet` `IModel.BasicPublish` `IModel.BasicConsume` `IModel.QueuePurge` `EventingBasicConsumer.HandleBasicDeliver` Minimum supported version: 3.5.2 Latest verified compatible version: 6.6.0
MassTransit (agent versions 10.19.0 and newer)	Message publish/send and consume Minimum supported version: 7.1.0 Latest verified compatible version: 8.5.0
AWSSDK.SQS (Amazon Simple Queue Service) (agent versions 10.27.0 and newer)	Message send and receive Minimum supported version: 3.7.0 Latest verified compatible version: 4.0.0.12
AWSSDK.Kinesis (Amazon Kinesis Data Streams) (agent versions 10.40.0 and newer)	The operations `PutRecord(s)Async` and `GetRecordsAsync` are instrumented as message broker operations. Other Kinesis operations are instrumented as basic method calls. Minimum supported version: 3.7.0 Latest verified compatible version: 4.0.2.10
AWSSDK.KinesisFirehose (Amazon Kinesis Firehose) (agent versions 10.40.0 and newer)	All Kinesis Firehose operations are instrumented as basic method calls. Minimum supported version: 3.7.0 Latest verified compatible version: 4.0.1.6
Azure Service Bus (Azure.Messaging.ServiceBus) (agent versions 10.42.0 and newer)	Message send and receive Supports Processor mode. The following methods are instrumented: `Azure.Messaging.ServiceBus.ReceiverManager.ProcessOneMessageWithinScopeAsync` `Azure.Messaging.ServiceBus.ServiceBusProcessor.OnProcessMessageAsync` `Azure.Messaging.ServiceBus.ServiceBusSender` `SendMessagesAsync` `ScheduleMessagesAsync` `CancelScheduledMessagesAsync` `Azure.Messaging.ServiceBus.ServiceBusReceiver` `ReceiveMessagesAsync` `ReceiveDeferredMessagesAsync` `PeekMessagesInternalAsync` `CompleteMessageAsync` `AbandonMessageAsync` `DeadLetterInternalAsync` `DeferMessageAsync` `RenewMessageLockAsync` Minimum supported version: 7.11.0 Latest verified compatible version: 7.18.2

Unavailable features

The following features are not available for the .NET agent:

The .NET agent does not support trim self-contained deployments and executables, because the compiler can potentially trim assemblies that the agent depends on.
Infinite Tracing is not supported on Alpine Linux due to a GRPC compatibility issue. See this agent issue for more information.

The .NET agent doesn't support Native Ahead of Time (AOT) deployment for .NET applications because just-in-time (JIT) compilation is required for the agent to function properly.

Connect the agent to other New Relic products

In addition to APM, the .NET agent integrates with other New Relic products to give you end-to-end visibility:

Product	Integration
Browser monitoring	For ASP.NET Core v6.0 and later web applications (MVC, Razor and Blazor), the .NET agent (starting with version 10.19.0) automatically injects the browser JavaScript agent when you enable auto-instrumentation. For other types of web applications, you can inject the agent by using the .NET agent API or the browser agent's copy/paste method. After enabling browser injection, you can view browser data in the APM Summary page and quickly switch between the APM and browser data for a particular app. For configuration options and manual instrumentation, see Browser monitoring and the .NET agent.
Infrastructure monitoring	When you install the infrastructure and APM agents on the same host, they automatically detect one another. You can then view a list of hosts in the APM UI, and filter your infrastructure hosts by APM app in our infrastructure UI. For more information, see APM data in the infrastructure UI.
Dashboards	The .NET agent sends default events and attributes for NRQL queries. You can also record custom events for advanced analysis.

Product

Integration

Browser monitoring

For ASP.NET Core v6.0 and later web applications (MVC, Razor and Blazor), the .NET agent (starting with version 10.19.0) automatically injects the browser JavaScript agent when you enable auto-instrumentation.

For other types of web applications, you can inject the agent by using the .NET agent API or the browser agent's copy/paste method.

After enabling browser injection, you can view browser data in the APM Summary page and quickly switch between the APM and browser data for a particular app. For configuration options and manual instrumentation, see Browser monitoring and the .NET agent.

Infrastructure monitoring

When you install the infrastructure and APM agents on the same host, they automatically detect one another. You can then view a list of hosts in the APM UI, and filter your infrastructure hosts by APM app in our infrastructure UI. For more information, see APM data in the infrastructure UI.

Dashboards

The .NET agent sends default events and attributes for NRQL queries. You can also record custom events for advanced analysis.

Requirements

Before you install New Relic's .NET agent, make sure your system meets these requirements:

.NET Framework 4.6.2 or higher

To instrument applications running on .NET Framework 4.6.2 or higher, you must run the New Relic .NET agent 10.0 or higher. To instrument applications running on .NET Framework version 4.0 or lower, you must run a version of the New Relic .NET agent lower than 7.0. For more information and download procedures, see Technical support for .NET frameworks 4.0 or lower.

The .NET agent doesn't support .NET Framework versions 4.5.1, 4.5.2, and 4.6.1

You must use one of these app/web servers:

IIS
Self-hosted OWIN
Self-hosted WCF
Kestrel
Kestrel with IIS reverse proxy via AspNetCoreModule
Kestrel with IIS reverse proxy via AspNetCoreModuleV2
The agent automatically creates transactions for apps hosted in IIS. If you self-host with WCF and OWIN version 3 or higher, the agent also automatically creates transactions. For other self-hosted services, you will need to create transactions via custom instrumentation.

Installation requires elevated privileges (Administrator). For example, you can:

Be logged in as an administrator user.
Be a member of the Administrators group.
On newer operating systems, provide elevation credentials when prompted.
The monitored process must have read/write access to the directory in which the agent is installed. The agent runs as a part of the monitored process and relies on those permissions to function.
Recommendation:
Restrict permissions for the newrelic.config file and give read/write access only to the owner of the monitored process.
Review permissions for the logs created by the agent to minimize the number of users with access and their privileges.

Automatic instrumentation

If your application is hosted in ASP.NET or another fully supported framework, the .NET agent will automatically instrument your application after install. If your app isn't automatically instrumented, or if you want to add instrumentation, use custom instrumentation.

The .NET agent doesn't directly monitor datastore processes. Also, by default the .NET SQL parameter capture in a query trace doesn't list parameters for a parameterized query or a stored procedure. Collection of the SQL query parameters can be enabled in the agent configuration.

The agent automatically instruments some application frameworks; we refer to these frameworks as fully supported, which are listed below:

ASP.NET MVC 2
ASP.NET MVC 3
ASP.NET MVC 4
ASP.NET MVC 5
ASP.NET Web API v2
ASP.NET Core MVC 2.0
ASP.NET Core 2.1
ASP.NET Core 2.2
ASP.NET Web Forms
Castle MonoRail v2 (No longer supported in the .NET Agent version 10.0 or higher)
OWIN-hosted web API applications on .NET framework using:
Microsoft.Owin.Host.HttpListener v2.x
Microsoft.Owin.Host.HttpListener v3.x
Microsoft.Owin.Host.HttpListener v4.x
SOAP-based web services
WCF

WCF Instrumentation has been tested for the following common binding types (both client and service). Varying levels of support are available for distributed tracing (DT) and cross application tracing (CAT):

Binding	Distributed Tracing (DT) Support	Cross Application Tracing (CAT) Support (Deprecated)
BasicHTTP	supported	supported
WebHTTP	supported	supported
WSHTTP	supported	supported
NetTCP	supported	supported
NetNamedPipe	not supported*	not supported*
NetMSMQ	not supported*	not supported*

* Distributed tracing may be manually implemented using these Distributed Tracing API methods.

Collecting instance details for supported datastores requires .NET agent version 6.5.29.0 or higher and is enabled by default. To request instance-level information from datastores not currently listed, get support at New Relic support center.

In order to automatically instrument the performance of .NET Framework application calls to these datastores, make sure you've the .NET agent version 8.14 or higher:

Datastore	Instance details	Other notes
Cosmos DB		The .NET agent `v9.2.0` or higher automatically instruments Microsoft.Azure.Cosmos library. Minimum supported version: 3.17.0 Latest verified compatible version: 3.52.0 Versions 3.35.0 and higher are supported beginning with .NET agent v10.32.0
Couchbase		Use CouchbaseNetClient. Minimum supported version: 2.0.0 Latest verified compatible version: 3.6.6 Version 3.2.0 and later are supported beginning with .NET agent v10.40.0 Known incompatible versions: 3.0.x, 3.1.x With CouchbaseNetClient 2.x, the following are not instrumented by default in favor of their multi-document counterparts: `Get(string key)` `GetDocument(string key)` `Remove(string key)` `Remove(string key, ulong cas)` `Upsert<T>(string key, T value)`
IBM DB2
Microsoft SQL Server		Use SqlClient from System.Data.SqlClient NuGet package or Microsoft.Data.SqlClient NuGet package or the Framework built-in System.Data assembly. System.Data.SqlClient Minimum supported version: 4.4.0 Latest verified compatible version: 4.8.6 Microsoft.Data.SqlClient Minimum supported version: 1.0.19239.1 Latest verified compatible version: 6.0.2 System.Data Minimum supported version: .NET Framework 4.6.2 Latest verified compatible version: 4.8
System.Data.ODBC		Use the built-in `System.Data.ODBC` namespace from the .NET Framework. Available in all currently supported .NET Framework agent versions. All versions of the .NET Framework currently supported by Microsoft are verified to be compatible.
MongoDB (legacy driver)		Minimum supported version: 1.10.0 Latest verified compatible version: 1.10.0 Known incompatible versions: Instance details aren't available in lower version 2.
MongoDB (modern driver)		Minimum supported version: 2.3.0 Latest verified compatible version: 3.3.0 Versions 3.0.0 and higher are supported beginning with .NET agent v10.40.0. Beginning in agent version 10.12.0, the following methods added in or after driver version 2.7 are instrumented: `IMongoCollection.CountDocuments[Async]` `IMongoCollection.EstimatedDocumentCount[Async]` `IMongoCollection.AggregateToCollection[Async]` `IMongoDatabase.ListCollectionNames[Async]` `IMongoDatabase.Aggregate[Async]` `IMongoDatabase.AggregateToCollection[Async]` `IMongoDatabase.Watch[Async]`
MySQL		Use MySql.Data or MySQL Connector MySql.Data Minimum supported version: 6.10.7 Latest verified compatible version: 9.3.0 MySqlConnector Minimum supported version: 1.0.1 Latest verified compatible version: 2.4.0
Oracle		Use Oracle.ManagedDataAccess Minimum supported version: 12.1.2400 Latest verified compatible version: 23.9.0
PostgreSQL		Use Npgsql Minimum supported version: 4.0.0 Latest verified compatible version: 4.0.5 Prior versions of Npgsql may also be instrumented, but duplicate and/or missing metrics are possible.
ServiceStack.Redis		Latest verified compatible version: 4.0.40 Known incompatible versions: 4.0.44 or higher
StackExchange.Redis		Minimum supported version: 1.0.488 Latest verified compatible version: 2.8.41
Elasticsearch		Use Elastic.Clients.Elasticsearch, NEST, or Elasticsearch.Net. Elastic.Clients.Elasticsearch Minimum supported version: 8.0.0 Maximum supported version: 8.15.10 Versions 8.10.0 and higher are supported beginning with .NET agent v10.20.1 Versions 8.12.1 and higher are supported beginning with .NET agent v10.23.0 NEST Minimum supported version: 7.0.0 Latest verified compatible version: 7.17.5 Elasticsearch.Net Minimum supported version: 7.0.0 Latest verified compatible version: 7.17.5
Memcached		Use EnyimMemcachedCore. Minimum supported version: 2.0.0 Latest verified compatible version: 3.4.0
DynamoDB		Use AWSSDK.DynamoDBv2. Minimum supported version: 3.5.0 Latest verified compatible version: 4.0.2 Minimum agent version required: 10.33.0

If your datastore isn't listed here, you can add custom instrumentation using the RecordDatastoreSegment method in the .NET agent API.

The agent automatically instruments these external call libraries:

Libraries	Supported methods
HttpClient	The agent instruments these HttpClient methods: `SendAsync` `GetAsync` `PostAsync` `PutAsync` `DeleteAsync` `GetStringAsync` `GetStreamAsync` `GetByteArrayAsync`
RestSharp	The agent instruments these RestSharp methods: `ExecuteTaskAsync` `ExecuteGetTaskAsync` `ExecutePostTaskAsync` `Execute` `ExecuteAsGet` `ExecuteAsPost` `DownloadData` Minimum supported version: 105.2.3 Latest verified compatible version: 112.1.0 Known incompatible versions: 106.8.0, 106.9.0, 106.10.0, 106.10.1
HttpWebRequest	The agent instruments these HttpWebRequest methods: `GetResponse`

Libraries

Supported methods

HttpClient

The agent instruments these HttpClient methods:

SendAsync
GetAsync
PostAsync
PutAsync
DeleteAsync
GetStringAsync
GetStreamAsync
GetByteArrayAsync

RestSharp

The agent instruments these RestSharp methods:

ExecuteTaskAsync
ExecuteGetTaskAsync
ExecutePostTaskAsync
Execute
ExecuteAsGet
ExecuteAsPost
DownloadData
Minimum supported version: 105.2.3
Latest verified compatible version: 112.1.0
Known incompatible versions: 106.8.0, 106.9.0, 106.10.0, 106.10.1

HttpWebRequest

The agent instruments these HttpWebRequest methods:

GetResponse

The .NET agent can be configured to automatically instrument these LLM frameworks:

Frameworks	Minimium framework version	Minimium agent version	Latest verified compatible version
AWS Bedrock	3.7.200.0	10.23.0 (`InvokeModelAsync`) 10.37.0 (`InvokeModelAsync`, `ConverseAsync`)	4.0.1
OpenAI	2.0.0	10.37.0 (`CompleteChat`, `CompleteChatAsync`)	2.1.0
Azure.AI.OpenAI	2.0.0	10.37.0 (`CompleteChat`, `CompleteChatAsync`)	2.1.0

The .NET agent can be configured to automatically instrument these logging frameworks for automatic logs-in-context with agent forwarding and local log decoration:

Frameworks	Minimium framework version	Minimium agent version	Latest verified compatible version
Log4Net	1.2.10	9.7.0	3.0.4
Serilog	2.0.0	9.7.0	4.3.0
NLog	4.1.0	9.7.0	6.0.1
Microsoft.Extensions.Logging	3.0.0	9.7.0	9.0.6

The agent automatically instruments these message systems:

Libraries	Supported methods
Confluent.Kafka	Produce and consume on topics. The following methods are instrumented: `IProducer.Produce` `IProducer.ProduceAsync` `IConsumer.Consume` Minimum supported version: 1.4.0 Latest verified compatible version: 2.10.1
MSMQ	Message send and receive, queue peek and purge
NServiceBus	Puts and takes on messages. Minimum supported version: 5.0 Latest verified compatible version: 8.2.4
RabbitMQ	Puts and takes on messages and queue purge. When receiving messages using an `IBasicConsumer`, the `EventingBasicConsumer` is the only implementation that is instrumented by the .NET agent. `BasicGet` is instrumented, but the agent does not support distributed tracing for `BasicGet`. The following methods are instrumented: `IModel.BasicGet` `IModel.BasicPublish` `IModel.BasicConsume` `IModel.QueuePurge` `EventingBasicConsumer.HandleBasicDeliver` Minimum supported version: 3.5.2 Latest verified compatible version: 6.6.0
MassTransit (agent versions 10.19.0 and newer)	Message publish/send and consume Minimum supported version: 7.1.0 Latest verified compatible version: 8.5.0
AWSSDK.SQS (Amazon Simple Queue Service) (agent versions 10.27.0 and newer)	Message send and receive Minimum supported version: 3.7.0 Latest verified compatible version: 4.0.0.12
AWSSDK.Kinesis (Amazon Kinesis Data Streams) (agent versions 10.40.0 and newer)	The operations `PutRecord(s)Async` and `GetRecordsAsync` are instrumented as message broker operations. Other Kinesis operations are instrumented as basic method calls. Minimum supported version: 3.7.0 Latest verified compatible version: 4.0.2.10
AWSSDK.KinesisFirehose (Amazon Kinesis Firehose) (agent versions 10.40.0 and newer)	All Kinesis Firehose operations are instrumented as basic method calls. Minimum supported version: 3.7.0 Latest verified compatible version: 4.0.1.6
Azure Service Bus (Azure.Messaging.ServiceBus) (agent versions 10.42.0 and newer)	Message send and receive Supports Processor mode. The following methods are instrumented: `Azure.Messaging.ServiceBus.ReceiverManager.ProcessOneMessageWithinScopeAsync` `Azure.Messaging.ServiceBus.ServiceBusProcessor.OnProcessMessageAsync` `Azure.Messaging.ServiceBus.ServiceBusSender` `SendMessagesAsync` `ScheduleMessagesAsync` `CancelScheduledMessagesAsync` `Azure.Messaging.ServiceBus.ServiceBusReceiver` `ReceiveMessagesAsync` `ReceiveDeferredMessagesAsync` `PeekMessagesInternalAsync` `CompleteMessageAsync` `AbandonMessageAsync` `DeadLetterInternalAsync` `DeferMessageAsync` `RenewMessageLockAsync` Minimum supported version: 7.11.0 Latest verified compatible version: 7.18.2

The listed .NET languages and technologies are compatible with our instant observability dashboards. If you use any of these languages or technologies, you can view your data in a New Relic dashboard, right out of the box:

Language/technology	Additional configuration
C# applications	New Relic can automatically instrument services written in C#. Go to our C# quickstart page to install the C# dashboards.
ADO.net	If your application uses ADO.net, you can install a combination of New Relic agents that generate an ADO.net dashboard. Here's what you need to do: Install the New Relic APM .NET agent and the infrastructure agent by following the steps in our guided installation. Install the Microsoft Windows Perfmon/WMI on-host integration for New Relic infrastructure by following the nri-perfmon instructions. If you installed Perfmon manually, restart your infrastructure agent. Go to our ADO.NET quickstart page to install the ADO.NET dashboards.
Blazor Server	Track your most important data in our Blazor Server dashboard by instrumenting your app with New Relic: Install the New Relic APM .NET agent and the infrastructure agent by following the steps in our guided installation. If you prefer, you can install the infrastructure agent via the command line. Get the pre-built dashboard by installing the Blazor quickstart From one.newrelic.com, go to APM & services, then select your app. To check that your installation is successful, query the following: `FROM Transaction SELECT count(*) FACET request.uri` If data appears, you've instrumented your app correctly.

Language/technology

Additional configuration

C# applications

New Relic can automatically instrument services written in C#. Go to our C# quickstart page to install the C# dashboards.

ADO.net

If your application uses ADO.net, you can install a combination of New Relic agents that generate an ADO.net dashboard. Here's what you need to do:

Install the New Relic APM .NET agent and the infrastructure agent by following the steps in our guided installation.
Install the Microsoft Windows Perfmon/WMI on-host integration for New Relic infrastructure by following the nri-perfmon instructions.
If you installed Perfmon manually, restart your infrastructure agent.
Go to our ADO.NET quickstart page to install the ADO.NET dashboards.

Blazor Server

Track your most important data in our Blazor Server dashboard by instrumenting your app with New Relic:

Install the New Relic APM .NET agent and the infrastructure agent by following the steps in our guided installation. If you prefer, you can install the infrastructure agent via the command line.
Get the pre-built dashboard by installing the Blazor quickstart
From one.newrelic.com, go to APM & services, then select your app. To check that your installation is successful, query the following:
```
FROM Transaction SELECT count(*) FACET request.uri
```
If data appears, you've instrumented your app correctly.

These frameworks are not fully supported:

ASP.NET Web API v1: See the troubleshooting information about using ASP.NET Web API v1 with New Relic's .NET agent 5.0 or higher for apps targeting .NET Framework 4.0. (This doesn't affect .NET Framework 4.5 or higher.)
Mono: New Relic doesn't support Mono, an open-source .NET framework that runs on Linux. This is because there is no Profiler API to inject into the .NET agent as a profiler into Mono-based .NET applications. The Profiler API is a Component Object Model (COM)-based interface and is not supported on Linux.
Classic ASP is not supported, because the agent can only instrument .NET Framework-based apps.
Sharepoint is not supported.

Unavailable features

Just-in-time (JIT) compilation is a requirement for .NET agent functionality, so native images created with Native Image Generator (NGEN) aren't supported by the .NET agent.

Connect the agent to other New Relic products

In addition to APM, the agent integrates with other New Relic products to give you end-to-end visibility:

Product	Integration
Browser monitoring	For ASP.NET web applications, the .NET agent automatically injects the browser JavaScript agent when you enable auto-instrumentation. After enabling browser injection, you can view browser data in the APM Summary page and quickly switch between the and data for a particular app. For configuration options and manual instrumentation, see Browser monitoring and the .NET agent.
Infrastructure monitoring	When you install the infrastructure and APM agents on the same host, they automatically detect one another. You can then view a list of hosts in the APM UI, and filter your hosts by APM app in our infrastructure UI. For more information, see APM data in infrastructure UI.
Dashboards	The .NET agent sends default events and attributes for NRQL queries. You can also record custom events for advanced analysis.
Synthetic monitoring	Synthetic transaction traces connect requests from synthetic monitors to the underlying APM transaction.

.NET agent: compatibility and requirements

Requirements .css-21sua1{background:none;border:none;width:0;padding:0;}

App/web servers

AWS Elastic Beanstalk

Microsoft Azure

Network requirements

Operating system

Permissions

Processor architectures

Security requirements

Target framework version

Automatic instrumentation

App frameworks

Datastores

External call libraries

Large Language Model (LLM)

Logging frameworks

Messaging

Unavailable features

Connect the agent to other New Relic products

Requirements

.NET Framework version

Application lifespan

App/web servers

AWS Elastic Beanstalk

CLRs

Code Access Security

Microsoft Azure

Network requirements

Operating system

Permissions

Processor architectures

Security requirements

Use of other monitoring software

Automatic instrumentation

App frameworks

Binding types

Datastores

CMS

External call libraries

Hosting Models

Invocation models

Large Language Model (LLM)

Logging frameworks

Messaging

Supported .NET languages and technologies for dashboards

Unsupported frameworks

Unavailable features

Connect the agent to other New Relic products

Requirements