Serilog.Extensions.Hosting 10.0.0

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
Alpata.Helper
Crypt işlemleri revize edildi.
32
Alpata.Helper
Option yönetimi için generik eklentiler sağlandı
19
Alpata.Helper
Option yönetimi için generik eklentiler sağlandı
23
Alpata.Helper
Option yönetimi için generik eklentiler sağlandı
29
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
19
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
20
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
21
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
22
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
24
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
28
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
31
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
198
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
639

Version Downloads Last updated
10.0.0 3 12/04/2025
10.0.0-dev-02310 4 12/04/2025
10.0.0-dev-02309 4 12/04/2025
9.0.1-dev-02307 10 02/25/2025
9.0.0 12 01/18/2025
9.0.0-dev-02303 14 01/18/2025
9.0.0-dev-02301 15 01/18/2025
8.0.0 30 03/01/2024
8.0.0-dev-00145 14 01/18/2025
8.0.0-dev-00143 14 03/28/2024
8.0.0-dev-00140 15 03/26/2024
8.0.0-dev-00137 16 03/16/2024
7.0.0 195 08/18/2023
7.0.0-dev-00131 14 03/04/2024
7.0.0-dev-00129 15 08/18/2023
7.0.0-dev-00126 19 03/04/2024
5.1.0-dev-00123 18 03/16/2024
5.0.1 644 08/18/2023
5.0.1-dev-00113 15 03/09/2024
5.0.0 17 03/03/2024
5.0.0-dev-00108 14 03/10/2024
5.0.0-dev-00095 14 03/14/2024
5.0.0-dev-00094 13 03/16/2024
5.0.0-dev-00093 13 03/16/2024
4.2.1-dev-00092 16 03/17/2024
4.2.0 28 08/18/2023
4.2.0-dev-00079 15 03/10/2024
4.1.2 15 03/17/2024
4.1.2-dev-00062 12 01/18/2025
4.1.1 15 03/14/2024
4.1.1-dev-00058 16 03/14/2024
4.1.0 18 03/03/2024
4.1.0-dev-00054 13 03/10/2024
4.0.0 17 03/04/2024
4.0.0-dev-00051 13 03/10/2024
4.0.0-dev-00050 13 03/10/2024
3.1.0 22 08/18/2023
3.1.0-dev-00041 17 03/17/2024
3.1.0-dev-00037 15 03/16/2024
3.1.0-dev-00035 13 03/16/2024
3.0.0 16 03/05/2024
3.0.0-dev-00024 14 03/10/2024
3.0.0-dev-00019 15 03/04/2024
3.0.0-dev-00016 14 03/09/2024
3.0.0-dev-00015 15 03/09/2024
2.0.1-dev-00009 14 03/16/2024
2.0.1-dev-00007 13 03/14/2024
2.0.1-dev-00004 13 03/13/2024
2.0.0 15 03/01/2024
2.0.0-dev-00001 13 03/04/2024