Serilog.Extensions.Hosting 9.0.0-dev-02301

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.

Inline initialization

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

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

This has the advantage of making builder'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
 2,272
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 118
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 62
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 59
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 58
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 57
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 56
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 54
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 52
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 51
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 50

.NET Framework 4.6.2

.NET 8.0

.NET 9.0

.NET Standard 2.0

.NET Standard 2.1

Version Downloads Last updated
11.0.0-dev-02501 0 11/12/2026
10.0.0 2,301 12/13/2025
10.0.0-dev-02310 48 12/31/2025
10.0.0-dev-02309 47 12/31/2025
9.0.1-dev-02307 45 12/12/2025
9.0.0 20 09/30/2026
9.0.0-dev-02303 45 12/11/2025
9.0.0-dev-02301 6 10/14/2026
8.0.0 128 09/28/2026
8.0.0-dev-00145 35 12/14/2025
8.0.0-dev-00143 41 12/15/2025
8.0.0-dev-00140 48 12/13/2025
8.0.0-dev-00137 42 12/13/2025
7.0.0 33 12/19/2025
7.0.0-dev-00131 38 12/14/2025
7.0.0-dev-00129 32 12/12/2025
7.0.0-dev-00126 35 12/11/2025
5.1.0-dev-00123 37 12/14/2025
5.0.1 41 12/14/2025
5.0.1-dev-00113 39 12/11/2025
5.0.0 39 12/13/2025
5.0.0-dev-00108 38 01/01/2026
5.0.0-dev-00095 40 12/12/2025
5.0.0-dev-00094 41 12/13/2025
5.0.0-dev-00093 37 12/28/2025
4.2.1-dev-00092 37 12/12/2025
4.2.0 42 12/12/2025
4.2.0-dev-00079 36 12/14/2025
4.1.2 9 09/28/2026
4.1.2-dev-00062 42 12/30/2025
4.1.1 44 12/13/2025
4.1.1-dev-00058 34 12/11/2025
4.1.0 3 10/20/2026
4.1.0-dev-00054 39 12/11/2025
4.0.0 39 12/13/2025
4.0.0-dev-00051 44 12/14/2025
4.0.0-dev-00050 7 10/02/2026
3.1.0 13 10/10/2026
3.1.0-dev-00041 40 01/02/2026
3.1.0-dev-00037 8 10/01/2026
3.1.0-dev-00035 35 12/13/2025
3.0.0 36 12/12/2025
3.0.0-dev-00024 43 12/13/2025
3.0.0-dev-00019 33 12/11/2025
3.0.0-dev-00016 38 12/12/2025
3.0.0-dev-00015 33 12/14/2025
2.0.1-dev-00009 37 12/12/2025
2.0.1-dev-00007 40 12/19/2025
2.0.1-dev-00004 41 01/01/2026
2.0.0 43 12/11/2025
2.0.0-dev-00001 7 10/11/2026