Serilog.Extensions.Hosting 9.0.0-dev-02303

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
AgileLabs
Package Description
 39
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 35
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 36
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 37
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 38
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 41
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 50
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 58
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 82
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 216

.NET Framework 4.6.2

.NET Standard 2.1

.NET Standard 2.0

.NET 9.0

.NET 8.0

Version Downloads Last updated
10.0.0 5 11/30/2025
10.0.0-dev-02310 3 11/30/2025
10.0.0-dev-02309 3 11/30/2025
9.0.1-dev-02307 25 02/27/2025
9.0.0 30 12/21/2024
9.0.0-dev-02303 23 12/05/2024
9.0.0-dev-02301 32 12/03/2024
8.0.0 246 04/23/2024
8.0.0-dev-00145 35 05/30/2024
8.0.0-dev-00143 33 05/30/2024
8.0.0-dev-00140 33 05/30/2024
8.0.0-dev-00137 37 04/26/2024
7.0.0 33 06/07/2023
7.0.0-dev-00131 32 05/30/2024
7.0.0-dev-00129 32 04/29/2024
7.0.0-dev-00126 29 11/07/2024
5.1.0-dev-00123 46 04/25/2024
5.0.1 89 12/14/2022
5.0.1-dev-00113 27 11/28/2024
5.0.0 31 05/23/2024
5.0.0-dev-00108 36 04/26/2024
5.0.0-dev-00095 32 05/05/2022
5.0.0-dev-00094 35 05/30/2024
5.0.0-dev-00093 33 05/17/2024
4.2.1-dev-00092 39 05/30/2024
4.2.0 14,040 04/14/2022
4.2.0-dev-00079 33 05/16/2024
4.1.2 197 04/25/2022
4.1.2-dev-00062 30 05/30/2024
4.1.1 31 04/30/2024
4.1.1-dev-00058 33 04/26/2024
4.1.0 35 05/07/2022
4.1.0-dev-00054 36 04/26/2024
4.0.0 31 04/26/2024
4.0.0-dev-00051 32 04/26/2024
4.0.0-dev-00050 36 04/26/2024
3.1.0 50 04/26/2024
3.1.0-dev-00041 28 11/14/2024
3.1.0-dev-00037 39 05/30/2024
3.1.0-dev-00035 37 05/22/2024
3.0.0 40 05/09/2024
3.0.0-dev-00024 40 05/30/2024
3.0.0-dev-00019 32 05/12/2024
3.0.0-dev-00016 38 05/05/2022
3.0.0-dev-00015 34 04/26/2024
2.0.1-dev-00009 26 05/30/2024
2.0.1-dev-00007 32 04/29/2024
2.0.1-dev-00004 29 04/26/2024
2.0.0 35 05/22/2024
2.0.0-dev-00001 34 04/26/2022