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
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 61
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 48
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 45
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 44
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 43
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 41
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 40
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 39
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 38
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 37
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 36

.NET Framework 4.6.2

.NET Standard 2.1

.NET Standard 2.0

.NET 9.0

.NET 8.0

Version Downloads Last updated
9.0.1-dev-02307 20 02/23/2025
9.0.0 21 12/10/2024
9.0.0-dev-02303 15 11/28/2024
9.0.0-dev-02301 15 12/07/2024
8.0.0 22 01/13/2024
8.0.0-dev-00145 24 04/07/2024
8.0.0-dev-00143 30 03/27/2024
8.0.0-dev-00140 32 03/17/2024
8.0.0-dev-00137 22 12/28/2023
7.0.0 50 06/12/2023
7.0.0-dev-00131 24 08/27/2023
7.0.0-dev-00129 21 08/31/2023
7.0.0-dev-00126 23 08/29/2023
5.1.0-dev-00123 26 08/29/2023
5.0.1 24 03/29/2023
5.0.1-dev-00113 21 08/28/2023
5.0.0 26 06/13/2023
5.0.0-dev-00108 24 08/28/2023
5.0.0-dev-00095 24 08/29/2023
5.0.0-dev-00094 24 08/30/2023
5.0.0-dev-00093 25 08/28/2023
4.2.1-dev-00092 24 08/24/2023
4.2.0 23 06/12/2023
4.2.0-dev-00079 22 08/28/2023
4.1.2 43 07/30/2021
4.1.2-dev-00062 19 08/30/2023
4.1.1 21 02/20/2024
4.1.1-dev-00058 25 08/28/2023
4.1.0 19 06/11/2023
4.1.0-dev-00054 23 08/28/2023
4.0.0 25 01/08/2024
4.0.0-dev-00051 22 08/28/2023
4.0.0-dev-00050 23 08/31/2023
3.1.0 36 07/21/2022
3.1.0-dev-00041 27 08/26/2023
3.1.0-dev-00037 24 08/25/2023
3.1.0-dev-00035 20 08/27/2023
3.0.0 21 06/13/2023
3.0.0-dev-00024 25 08/29/2023
3.0.0-dev-00019 21 08/28/2023
3.0.0-dev-00016 27 08/27/2023
3.0.0-dev-00015 25 08/26/2023
2.0.1-dev-00009 44 08/30/2023
2.0.1-dev-00007 27 08/29/2023
2.0.1-dev-00004 22 08/25/2023
2.0.0 21 06/12/2023
2.0.0-dev-00001 28 08/30/2023