New Relic offers a .NET Framework agent and a .NET Core agent. The .NET Core agent includes built-in instrumentation for the most popular components of the Microsoft .NET Core ecosystem. After installation, the agent runs within the monitored process; there is not a separate process or service created by the agent.
If your application is not automatically instrumented, you can custom instrument it to report data to New Relic.
Before you install the New Relic for .NET Core agent, make sure your system meets these requirements:
The .NET Core agent supports .NET Core version 2.0, 2.1, 2.2, and 3.0 preview.
The agent is not compatible with .NET Core versions 1.0 or 1.1. For .NET Core 2.1 or higher applications with tiered compilation enabled, the agent will disable tiered compilation. .NET Core 2.1 support requires .NET Core runtime 2.1.3 and .NET Core SDK 2.1.401 or higher due to a bug in the .NET Core profiling API.
The .NET Core agent only supports applications targeting .NET Core 2.0, 2.1, 2.2, and 3.0 preview. You can find the target framework in your
If you want to monitor an ASP.NET Core application targeting the .NET Framework, you must use the Framework agent.
Ensure you use one of these app/web servers:
- Kestrel with IIS reverse proxy via AspNetCoreModule
- Kestrel with IIS reverse proxy via AspNetCoreModuleV2
- Kestrel with Nginx reverse proxy
- Kestrel with Apache reverse proxy
The agent has been verified to work with the following operating systems:
Operating system Supported versions Windows
- Server 2008 R2 SP1
- Server 2012
- Server 2012 R2
- Server 2016
- Server 2019
- Windows containers running on Server 2016 (NanoServer based images are not supported)
Linux (x64 only)
All x64 Linux distributions supported by .NET Core Runtime are supported by the .NET Core agent. For a full list, refer to Microsoft's documentation for the version of the runtime you are using.
- Microsoft Azure
For Azure-specific installation instructions, see:
The agent is available in both 32-bit (x86) and 64-bit versions on Windows as well as 64-bit on Linux.
Installing and running the .NET Core 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_IUSRSis often used.
As a standard security measure for data collection, your app server must support SHA-2 (256-bit). SHA-1 is not supported.
The agent requires your firewall to allow outgoing connections to specific networks and ports.
You can install a .NET Framework agent and a .NET Core agent side-by-side on the same system; they must be in separate directories.
If your application is hosted in ASP.NET Core, the agent automatically creates and instruments transactions. the .NET Core agent will automatically instrument your application after install. If your app is not automatically instrumented, or if you want to add instrumentation, use custom instrumentation.
In order to automatically instrument these frameworks and features, make sure you have the .NET agent version 8.14 or higher:
The .NET Core agent automatically instruments these application frameworks:
- ASP.NET Core MVC 2.0, 2.1, 2.2, and 3.0 preview 2 (includes Web API)
The .NET Core agent automatically instruments the performance of .NET application calls to these datastores:
Datastore Instance details Notes Microsoft SQL (MSSQL) Server fa-check Use System.Data.SqlClient version 4.3.1 or Microsoft.Data.SqlClient. PostgresSQL fa-check
Use Npgsql 4.0.
Prior versions of Npgsql may also be instrumented, but duplicate and/or missing metrics are possible.
Driver version 2.7.x: The .NET agent will support pre-existing API methods, but not new methods introduced in 2.7.x.
MySQL fa-check Use MySql.Data version 6.10.4.
The .NET Core 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.
The .NET Core agent automatically instruments these external call libraries :
Libraries Supported methods HttpClient
The agent instruments these HttpClient methods:
The following features are not available for the .NET Core agent:
- Thread profiling on Linux (thread profiling on Windows is supported)
- Memory usage on Linux due to an ongoing .NET Core issue
- Automatic New Relic Browser script injection (API or manual instrumentation is required)
Connect the agent to other New Relic products
In addition to New Relic APM, the .NET Core agent integrates with other New Relic products to give you end-to-end visibility:
|New Relic Browser||
After enabling Browser injection, you can view Browser data in the APM Overview page and quickly switch between the APM and Browser data for a particular app. For configuration options and manual instrumentation, see New Relic Browser and the .NET agent.
|New Relic Infrastructure||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 the Infrastructure UI. For more information, see New Relic APM data in Infrastructure.|
|New Relic Insights||The .NET agent sends default events and attributes to Insights for NRQL queries. You can also record custom events for advanced analysis.|