Our .NET agent supports both .NET Framework and .NET Core. Here we describe the compatibility and support for .NET Framework applications. For .NET Core, see Compatibility and requirements for .NET Core.
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.
Want to try out New Relic's .NET agent? Create a New Relic account for free! No credit card required.
Before you install New Relic's .NET agent, make sure your system meets these requirements:
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.
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:
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.
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.
Synthetic transaction traces connect requests from synthetic monitors to the underlying APM transaction.