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
 39
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 40
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 41
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 42
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 45
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 46
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 98
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 134
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 217
Serilog.AspNetCore.Plus
Serilog support for ASP.NET Core logging with some plus features
 89

.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.0 5 12/17/2024
9.0.0-dev-02303 6 12/08/2024
9.0.0-dev-02301 6 12/08/2024
8.0.0 112 02/04/2024
8.0.0-dev-00145 34 07/22/2024
8.0.0-dev-00143 31 07/22/2024
8.0.0-dev-00140 29 07/22/2024
8.0.0-dev-00137 45 07/22/2024
7.0.0 42 02/05/2024
7.0.0-dev-00131 34 07/22/2024
7.0.0-dev-00129 29 07/22/2024
7.0.0-dev-00126 33 07/22/2024
5.1.0-dev-00123 43 07/22/2024
5.0.1 103 02/04/2024
5.0.1-dev-00113 41 07/22/2024
5.0.0 28 07/22/2024
5.0.0-dev-00108 30 07/22/2024
5.0.0-dev-00095 41 07/22/2024
5.0.0-dev-00094 31 07/22/2024
5.0.0-dev-00093 30 07/22/2024
4.2.1-dev-00092 36 07/22/2024
4.2.0 77 02/04/2024
4.2.0-dev-00079 40 07/22/2024
4.1.2 41 07/22/2024
4.1.2-dev-00062 40 07/22/2024
4.1.1 39 07/22/2024
4.1.1-dev-00058 37 07/22/2024
4.1.0 36 07/22/2024
4.1.0-dev-00054 34 07/22/2024
4.0.0 34 07/22/2024
4.0.0-dev-00051 44 07/22/2024
4.0.0-dev-00050 38 07/22/2024
3.1.0 28 07/22/2024
3.1.0-dev-00041 26 07/22/2024
3.1.0-dev-00037 34 07/22/2024
3.1.0-dev-00035 35 07/22/2024
3.0.0 28 07/22/2024
3.0.0-dev-00024 47 07/22/2024
3.0.0-dev-00019 31 07/22/2024
3.0.0-dev-00016 37 07/22/2024
3.0.0-dev-00015 46 07/22/2024
2.0.1-dev-00009 31 07/22/2024
2.0.1-dev-00007 45 07/22/2024
2.0.1-dev-00004 30 07/22/2024
2.0.0 40 07/22/2024
2.0.0-dev-00001 39 07/22/2024