Serilog.Extensions.Hosting 10.0.0-dev-02309

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
76
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
66
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
67
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
68
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
69
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
70
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
72
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
78
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
101
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
106
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
124
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
272

Version Downloads Last updated
10.0.0 32 11/30/2025
10.0.0-dev-02310 24 11/30/2025
10.0.0-dev-02309 26 11/30/2025
9.0.1-dev-02307 50 02/27/2025
9.0.0 55 12/21/2024
9.0.0-dev-02303 46 12/05/2024
9.0.0-dev-02301 61 12/03/2024
8.0.0 311 04/23/2024
8.0.0-dev-00145 55 05/30/2024
8.0.0-dev-00143 56 05/30/2024
8.0.0-dev-00140 57 05/30/2024
8.0.0-dev-00137 66 04/26/2024
7.0.0 58 06/07/2023
7.0.0-dev-00131 59 05/30/2024
7.0.0-dev-00129 53 04/29/2024
7.0.0-dev-00126 60 11/07/2024
5.1.0-dev-00123 67 04/25/2024
5.0.1 126 12/14/2022
5.0.1-dev-00113 58 11/28/2024
5.0.0 59 05/23/2024
5.0.0-dev-00108 58 04/26/2024
5.0.0-dev-00095 52 05/05/2022
5.0.0-dev-00094 58 05/30/2024
5.0.0-dev-00093 58 05/17/2024
4.2.1-dev-00092 59 05/30/2024
4.2.0 14,332 04/14/2022
4.2.0-dev-00079 58 05/16/2024
4.1.2 233 04/25/2022
4.1.2-dev-00062 59 05/30/2024
4.1.1 56 04/30/2024
4.1.1-dev-00058 60 04/26/2024
4.1.0 66 05/07/2022
4.1.0-dev-00054 57 04/26/2024
4.0.0 52 04/26/2024
4.0.0-dev-00051 53 04/26/2024
4.0.0-dev-00050 60 04/26/2024
3.1.0 72 04/26/2024
3.1.0-dev-00041 52 11/14/2024
3.1.0-dev-00037 59 05/30/2024
3.1.0-dev-00035 55 05/22/2024
3.0.0 67 05/09/2024
3.0.0-dev-00024 60 05/30/2024
3.0.0-dev-00019 49 05/12/2024
3.0.0-dev-00016 65 05/05/2022
3.0.0-dev-00015 60 04/26/2024
2.0.1-dev-00009 49 05/30/2024
2.0.1-dev-00007 60 04/29/2024
2.0.1-dev-00004 50 04/26/2024
2.0.0 60 05/22/2024
2.0.0-dev-00001 60 04/26/2022