Build status NuGet Samples

Logging to from Entity Framework Core

Both and Entity Framework Core supports logging through Microsoft.Extensions.Logging. To log all errors happening inside Entity Framework Core, install the Elmah.Io.Extensions.Logging NuGet package:

Install-Package Elmah.Io.Extensions.Logging
dotnet add package Elmah.Io.Extensions.Logging
<PackageReference Include="Elmah.Io.Extensions.Logging" Version="5.*" />
paket add Elmah.Io.Extensions.Logging

Then add to a new or existing LoggerFactory:

var loggerFactory = new LoggerFactory()
    .AddElmahIo("API_KEY", new Guid("LOG_ID"));

Replace API_KEY with your API key (Where is my API key?) and LOG_ID with the log ID (Where is my log ID?) that should receive errors from Entity Framework.

When using Entity Framework Core from ASP.NET Core, you never create a LoggerFactory. Factories are provided through DI by ASP.NET Core. Check out this sample for details.

Finally, enable logging in Entity Framework Core:


(UseSqlServer included for illustration purposes only - works with any provider)

That's it! All errors happening in Entity Framework Core, are now logged in

Logging from interceptors

Interceptors in Entity Framework are hooks/events that you can implement to get notified when different actions happen towards your database. Interceptors can be used for a range of tasks like maintaining created/modified dates, calculating fields on save, logging, and many more.

To illustrate how interceptors can be used to enrich with custom log messages, the following code shows how to create a simple audit log of creating new users in the database. The code for the interceptor could look similar to this:

public class SaveUsersAuditLog : SaveChangesInterceptor
    private readonly ILogger<SaveUsersAuditLog> logger;

    public SaveUsersAuditLog(ILogger<SaveUsersAuditLog> logger)
        this.logger = logger;

    public override int SavedChanges(SaveChangesCompletedEventData eventData, int result)
        var dbContext = eventData.Context;
        foreach (var entry in dbContext
            .Where(user => user.State == EntityState.Added))
            using (logger.BeginScope(new Dictionary<string, object> { { "DebugView", entry.DebugView.LongView } }))
                logger.LogInformation("Adding user with {UserId}", entry.Entity.Id);

        return base.SavedChanges(eventData, result);

The class extends SaveChangesIntercepter and overrides the SavedChanges method. This will be called by Entity Framework when entities are saved to the database. By filtering on the entity state Added, you can log a custom message for all new users added to the database. In the example, the message Adding user with {UserId} is logged and the value of the Id property is used as part of the structured log message. In addition, the code uses scopes in Microsoft.Extensions.Logging to log an additional property named DebugView with the long debug message provided by Entity Framework. This key/value will show up on the Data tab within the UI.

Be careful when logging entities that may contain personal identifiable data (PID). Adding debug messages from Entity Framework will contain this PID and share it with

Registering interceptors varies by the way you set up Entity Framework. Following the code in the first parts of this page, you can create a logger and register the interceptor like this:

var logger = loggerFactory.CreateLogger<SaveUsersAuditLog>();
optionsBuilder.AddInterceptors(new SaveUsersAuditLog(logger));

This article was brought to you by the team. is the best error management system for .NET web applications. We monitor your website, alert you when errors start happening, and help you fix errors fast.

See how we can help you monitor your website for crashes Monitor your website