With our .NET agent for application performance monitoring, you can:
- Use APM to get a high-level overview of your app, to see code-level details like transaction traces, database queries, and errors, and to track activity across a large distributed system.
- Get proactive notifications from alerts to ensure your app is up and running smoothly.
- Use the query builder to query your data and create custom dashboards with that data.
- Install infrastructure monitoring to view the performance of your app's host environment.
The agent's support for .NET Core takes advantage of the compatibility, speed, expanded API features, and cross-platform capabilities of Microsoft's .NET Core. The agent does not support Microsoft .NET Core versions earlier than 2.0.
With New Relic's support for .NET, 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
- AWS EC2 VMs
Our guided install creates a customized CLI command for your environment that downloads and installs the .NET agent for Windows IIS applications.
Ready to get started? Click the Guided install button. If your account reports data through our EU datacenter, click EU Guided install.
In addition to the .NET agent, you can use this to install our infrastructure agent to discover other applications, infrastructure, and log sources running in your environment and recommend which ones should be instrumented. The install automates the configuration and deployment of each system you choose to instrument.
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 APM Summary page. If you have problems, see No data appears and the other troubleshooting docs in that section.
one.newrelic.com > APM > (select an app) > Summary: After installing the .NET agent, you will see a summary of your app's performance on the Summary page.
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.
After installing the .NET agent, extend the agent's instrumentation with one or more of these methods:
Integrate the .NET agent with browser monitoring to gain visibility into end-user activity.
Instrument transactions not captured as part of New Relic's automatic framework instrumentation.
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.
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.
Enable distributed tracing to understand activity across a complex, distributed system that uses many services and microservices.
You can also bring your logs and application's data together to make troubleshooting easier and faster. With logs in context, you can see log messages related to your errors and traces directly in your app's UI. You can also see logs in context of your infrastructure data, such as Kubernetes clusters. No need to switch to another UI page.