There are many tools that provide APM (Application Performance Monitoring) for Asp.NET.
The all share the same steps and configuration on how to hook their service into Asp.NET running instance.

How profiling work in .NET

Profiling a managed CLR application is different than profiling normal non-managed appication, because CLR is different. CLR prvides these services:

• Application domains
• Garbage collection
• Managed exception handling
• Just In Time (JIT) compilation

.NET provides its own profiling API, and all profiling tools are using this API, and they all work in the same way.
When a managed application starts, it loads the CLR, and when the CLR initialized, it looks for these two environment variables:

• CORECLR_ENABLE_PROFILING
• CORECLR_PROFILER The CORECLR_ENABLE_PROFILING should be 1, and the CORECLR_PROFILER is a GUID that unique for a specific APM provider.
  If profiling is enabled, CLR will look for the profiling library and load it. The profiling library will be provided by another environment variable, or variables:

Hosting your application on Azure

If you are hosting your application on Azure, then we will list the above environment variable values:

Using Azure Application Insight:

You can use Azure Application Insight which will provide an easy way to configure the application.
From Azure or from Bicep, you can attach Application Insight to your app, and everything will be configured automatically.

Example NewRelic:

• Previous
  Self certified certificates
• Next
  Managing Credentials for Azure Artifacts