Introduction to New Relic for .NET

With New Relic APM for .NET, you can monitor your .NET applications and services. In this introduction to New Relic APM for .NET, you'll learn the reasons to use this product, and how to get started using it.

Features

After you install the New Relic .NET agent, you can:

Support for both .NET Framework and .NET Core

New Relic offers both a .NET Framework agent and a .NET Core agent.

New Relic's .NET Framework agent works with all .NET compatible languages, such as VB.NET, C#, and CLI.

The .NET Core agent takes advantage of the compatibility, speed, expanded API features, and cross-platform capabilities of Microsoft's .NET Core. The .NET Core agent does not support Microsoft .NET Core versions earlier than 2.0. With New Relic's .NET Core agent, you can monitor your apps in dynamic or distributed environments, such as:

  • Cloud-managed server VM images
  • On-host VM servers
  • Microsoft Azure App Services
  • Self-hosted Windows and Linux systems
  • Amazon AWS EC2 VMs

The .NET Core agent instruments Microsoft .NET Core processes to monitor apps on both Linux and Windows operating systems, including auto-instrumentation of web and external calls, Kestrel web transactions, and more.

Install the agent

Before you install a .NET agent, create your New Relic account. Then, review the .NET Framework agent system requirements or the .NET Core agent system requirements. When you are ready to install, see the .NET agent install overview.

To stay up-to-date with new features and bug fixes, see the .NET agent release notes.

After you install the agent and wait a few minutes for your app to generate traffic, data will appear in the New Relic APM Overview page. If no data appears, or if you encounter other problems, see New Relic's .NET troubleshooting procedures.

screen-dotnet-apm-overview-page.png
rpm.newrelic.com/apm > (select an app) > Overview: After installing the .NET agent, you will see a summary of your app's performance on the Overview page.

Configure the agent

The most important part of agent configuration is to give your app a descriptive name. New Relic uses this app name to aggregate metrics when you have multiple apps or hosts. The agent also includes a variety of configuration options to further customize your installation.

Extend your instrumentation

After installing the .NET agent, extend the agent's instrumentation with one or more of these methods:

Instrumentation options Details
Browser instrumentation

Integrate the .NET agent with New Relic Browser to gain visibility into end-user activity.

Custom instrumentation Instrument transactions not captured as part of New Relic's automatic framework instrumentation.
Agent API See the .NET agent API guide to learn how to customize the agent's behavior. For example, you can collect custom metrics, flag an error, or ignore a particular transaction entirely.
Custom attributes Customize the attributes attached to transactions. Customizing attributes allows you to avoid sending sensitive attributes, or to collect additional attributes for deeper visibility into your transactions.
Distributed tracing Enable distributed tracing to understand activity across a complex, distributed system that uses many services and microservices.

For more help

Recommendations for learning more: