Set up ASP.NET Core instrumentation

For the full compatibility matrix including supported installation methods, refer to Web frameworks.

For ASP.NET Core, once you reference the Elastic.Apm.NetCoreAll package, you can enable every agent component by calling the AddAllElasticApm() extension method on the IServiceCollection in the Program.cs file.

var builder = WebApplication.CreateBuilder(args);

builder.Services.AddAllElasticApm();

var app = builder.Build();

// Configure the HTTP request pipeline.

app.Run();

With this you enable every agent component including ASP.NET Core tracing, monitoring of outgoing HTTP request, Entity Framework Core database tracing, and so on.

In case you only reference the Elastic.Apm.AspNetCore package, you won’t find the AddAllElasticApm. Instead you need to use the AddElasticApmForAspNetCore() method. This method turns on ASP.NET Core tracing, and gives you the opportunity to manually turn on other components. By default it will only trace ASP.NET Core requests - No HTTP request tracing, database call tracing or any other tracing component will be turned on.

In case you would like to turn on specific tracing components you can pass those to the AddElasticApm method.

For example:

using Elastic.Apm.DiagnosticSource;
using Elastic.Apm.EntityFrameworkCore;

builder.Services.AddElasticApm(
    new HttpDiagnosticsSubscriber(),  /* Enable tracing of outgoing HTTP requests */
    new EfCoreDiagnosticsSubscriber()); /* Enable tracing of database calls through EF Core*/

1. for HttpDiagnosticsSubscriber
2. for EfCoreDiagnosticsSubscriber

In case you only want to use the Public API, you don’t need to do any initialization, you can start using the API and the agent will send the data to the APM Server.

After adding the agent, configure it to connect to your APM Server. The fastest way is through environment variables or appsettings.json. See Minimum configuration for the three settings every deployment needs.

To set configuration values programmatically, for example to derive the APM service name or environment from other application configuration, see Overriding configuration values programmatically.