Serilog.Extensions.Hosting 8.0.0-dev-00145

Serilog.Extensions.Hosting Build status NuGet Version

Serilog logging for Microsoft.Extensions.Hosting. This package routes framework log messages through Serilog, so you can get information about the framework's internal operations written to the same Serilog sinks as your application events.

Versioning: This package tracks the versioning and target framework support of its Microsoft.Extensions.Hosting dependency. Most users should choose the version of Serilog.Extensions.Hosting that matches their application's target framework. I.e. if you're targeting .NET 7.x, choose a 7.x version of Serilog.Extensions.Hosting. If you're targeting .NET 8.x, choose an 8.x Serilog.Extensions.Hosting version, and so on.

Instructions

First, install the Serilog.Extensions.Hosting NuGet package into your app. You will need a way to view the log messages - Serilog.Sinks.Console writes these to the console; there are many more sinks available on NuGet.

dotnet add package Serilog.Extensions.Hosting
dotnet add package Serilog.Sinks.Console

Next, in your application's Program.cs file, configure Serilog first. A try/catch block will ensure any configuration issues are appropriately logged. Call AddSerilog() on the host application builder:

using Serilog;

Log.Logger = new LoggerConfiguration()
    .Enrich.FromLogContext()
    .WriteTo.Console()
    .CreateLogger();

try
{
    Log.Information("Starting host");

    var builder = Host.CreateApplicationBuilder(args);
    builder.Services.AddHostedService<PrintTimeService>();
    builder.Services.AddSerilog();

    var app = builder.Build();
    
    await app.RunAsync();
    return 0;
}
catch (Exception ex)
{
    Log.Fatal(ex, "Host terminated unexpectedly");
    return 1;
}
finally
{
    await Log.CloseAndFlushAsync();
}

Finally, clean up by removing the remaining "Logging" section from appsettings.json files (this can be replaced with Serilog configuration as shown in this example, if required)

That's it! You will see log output like:

[22:10:39 INF] Getting the motors running...
[22:10:39 INF] The current time is: 12/05/2018 10:10:39 +00:00

A more complete example, showing appsettings.json configuration, can be found in the sample project here.

Using the package

With Serilog.Extensions.Hosting installed and configured, you can write log messages directly through Serilog or any ILogger interface injected by .NET. All loggers will use the same underlying implementation, levels, and destinations.

Tip: change the minimum level for Microsoft to Warning

Inline initialization

You can alternatively configure Serilog using a delegate as shown below:

    // dotnet add package Serilog.Settings.Configuration
    .UseSerilog((hostingContext, services, loggerConfiguration) => loggerConfiguration
        .ReadFrom.Configuration(hostingContext.Configuration)
        .Enrich.FromLogContext()
        .WriteTo.Console())

This has the advantage of making the hostingContext's Configuration object available for configuration of the logger, but at the expense of ignoring Exceptions raised earlier in program startup.

If this method is used, Log.Logger is assigned implicitly, and closed when the app is shut down.

Showing the top 20 packages that depend on Serilog.Extensions.Hosting.

Packages Downloads
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 967
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 815
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 208
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 183
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 155
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 26
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 15
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 14

.NET Framework 4.6.2

.NET Standard 2.0

.NET 8.0

.NET 7.0

.NET 6.0

Version Downloads Last updated
10.0.0 7 12/11/2025
10.0.0-dev-02310 8 12/10/2025
10.0.0-dev-02309 8 12/10/2025
9.0.1-dev-02307 13 02/20/2025
9.0.0 139 02/19/2025
9.0.0-dev-02303 14 02/19/2025
9.0.0-dev-02301 13 05/24/2025
8.0.0 1,635 08/06/2024
8.0.0-dev-00145 13 05/24/2025
8.0.0-dev-00143 13 05/24/2025
8.0.0-dev-00140 14 02/19/2025
8.0.0-dev-00137 13 05/24/2025
7.0.0 14 02/19/2025
7.0.0-dev-00131 14 02/19/2025
7.0.0-dev-00129 13 05/24/2025
7.0.0-dev-00126 13 05/24/2025
5.1.0-dev-00123 14 02/20/2025
5.0.1 125 08/06/2024
5.0.1-dev-00113 13 05/24/2025
5.0.0 14 02/19/2025
5.0.0-dev-00108 14 02/19/2025
5.0.0-dev-00095 14 02/19/2025
5.0.0-dev-00094 14 02/19/2025
5.0.0-dev-00093 14 02/19/2025
4.2.1-dev-00092 14 02/20/2025
4.2.0 14 02/19/2025
4.2.0-dev-00079 13 05/24/2025
4.1.2 14 02/19/2025
4.1.2-dev-00062 14 02/20/2025
4.1.1 15 02/19/2025
4.1.1-dev-00058 14 02/20/2025
4.1.0 14 02/19/2025
4.1.0-dev-00054 13 05/24/2025
4.0.0 14 02/19/2025
4.0.0-dev-00051 14 02/19/2025
4.0.0-dev-00050 14 02/19/2025
3.1.0 14 02/19/2025
3.1.0-dev-00041 14 02/19/2025
3.1.0-dev-00037 14 02/19/2025
3.1.0-dev-00035 14 02/19/2025
3.0.0 14 02/19/2025
3.0.0-dev-00024 14 02/19/2025
3.0.0-dev-00019 14 02/19/2025
3.0.0-dev-00016 14 02/19/2025
3.0.0-dev-00015 14 02/19/2025
2.0.1-dev-00009 14 02/19/2025
2.0.1-dev-00007 14 02/19/2025
2.0.1-dev-00004 14 02/19/2025
2.0.0 14 02/19/2025
2.0.0-dev-00001 14 02/19/2025