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
5,210
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
517
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
304
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
69
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
63
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
61
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
60
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
55
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
54

Version Downloads Last updated
9.0.1-dev-02307 34 02/20/2025
9.0.0 40 12/12/2024
9.0.0-dev-02303 36 12/02/2024
9.0.0-dev-02301 41 12/01/2024
8.0.0 5,432 11/24/2023
8.0.0-dev-00145 59 04/07/2024
8.0.0-dev-00143 51 04/04/2024
8.0.0-dev-00140 48 04/04/2024
8.0.0-dev-00137 53 11/29/2023
7.0.0 514 06/30/2023
7.0.0-dev-00131 51 09/23/2023
7.0.0-dev-00129 60 08/15/2023
7.0.0-dev-00126 56 08/16/2023
5.1.0-dev-00123 62 08/10/2023
5.0.1 64 12/30/2022
5.0.1-dev-00113 64 07/28/2023
5.0.0 57 08/24/2023
5.0.0-dev-00108 61 08/21/2023
5.0.0-dev-00095 57 08/22/2023
5.0.0-dev-00094 56 07/30/2023
5.0.0-dev-00093 59 08/24/2023
4.2.1-dev-00092 54 10/31/2022
4.2.0 58 06/15/2022
4.2.0-dev-00079 60 08/04/2023
4.1.2 56 08/24/2023
4.1.2-dev-00062 59 06/17/2023
4.1.1 63 06/16/2023
4.1.1-dev-00058 58 08/17/2023
4.1.0 55 02/03/2023
4.1.0-dev-00054 69 06/06/2023
4.0.0 63 08/19/2023
4.0.0-dev-00051 57 08/23/2023
4.0.0-dev-00050 62 08/23/2023
3.1.0 56 09/05/2023
3.1.0-dev-00041 61 08/15/2023
3.1.0-dev-00037 63 12/04/2022
3.1.0-dev-00035 49 08/17/2023
3.0.0 64 06/18/2023
3.0.0-dev-00024 61 08/17/2023
3.0.0-dev-00019 67 08/15/2023
3.0.0-dev-00016 58 08/19/2023
3.0.0-dev-00015 57 08/09/2023
2.0.1-dev-00009 54 08/28/2023
2.0.1-dev-00007 62 08/04/2023
2.0.1-dev-00004 55 08/22/2023
2.0.0 65 08/24/2023
2.0.0-dev-00001 58 08/14/2023