Serilog.Extensions.Hosting 8.0.0-dev-00140

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.

ASP.NET Core applications should consider using Serilog.AspNetCore instead, which bundles this package and includes other ASP.NET Core-specific features.

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:

public class Program
{
    public static int Main(string[] args)
    {
        Log.Logger = new LoggerConfiguration()
            .MinimumLevel.Debug()
            .MinimumLevel.Override("Microsoft", LogEventLevel.Information)
            .Enrich.FromLogContext()
            .WriteTo.Console()
            .CreateLogger();

        try
        {
            Log.Information("Starting host");
            BuildHost(args).Run();
            return 0;
        }
        catch (Exception ex)
        {
            Log.Fatal(ex, "Host terminated unexpectedly");
            return 1;
        }
        finally
        {
            Log.CloseAndFlush();
        }
    }

Then, add UseSerilog() to the host builder in BuildHost().

    public static IHost BuildHost(string[] args) =>
        new HostBuilder()
            .ConfigureServices(services => services.AddSingleton<IHostedService, PrintTimeService>())
            .UseSerilog() // <- Add this line
            .Build();
}

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.

Tip: change the minimum level for Microsoft to Warning

Inline initialization

You can alternatively configure Serilog using a delegate as shown below:

    // dotnet add package Serilog.Settings.Configuration
    .UseSerilog((hostingContext, services, loggerConfiguration) => loggerConfiguration
        .ReadFrom.Configuration(hostingContext.Configuration)
        .Enrich.FromLogContext()
        .WriteTo.Console())

This has the advantage of making the hostingContext'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.

Versioning

This package tracks the versioning and target framework support of its Microsoft.Extensions.Hosting dependency.

Showing the top 20 packages that depend on Serilog.Extensions.Hosting.

Packages Downloads
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 1,023
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 24
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 21
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 17
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 16
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
 15

.NET Framework 4.6.2

.NET 6.0

.NET 7.0

.NET 8.0

.NET Standard 2.0

Version Downloads Last updated
10.0.0 17 12/13/2025
10.0.0-dev-02310 14 12/31/2025
10.0.0-dev-02309 12 12/31/2025
9.0.1-dev-02307 17 12/12/2025
9.0.0 11 12/10/2025
9.0.0-dev-02303 18 12/11/2025
9.0.0-dev-02301 12 12/10/2025
8.0.0 1,022 12/10/2025
8.0.0-dev-00145 11 12/14/2025
8.0.0-dev-00143 15 12/15/2025
8.0.0-dev-00140 13 12/13/2025
8.0.0-dev-00137 16 12/13/2025
7.0.0 10 12/19/2025
7.0.0-dev-00131 16 12/14/2025
7.0.0-dev-00129 14 12/12/2025
7.0.0-dev-00126 12 12/11/2025
5.1.0-dev-00123 16 12/14/2025
5.0.1 11 12/14/2025
5.0.1-dev-00113 15 12/11/2025
5.0.0 13 12/13/2025
5.0.0-dev-00108 13 01/01/2026
5.0.0-dev-00095 12 12/12/2025
5.0.0-dev-00094 17 12/13/2025
5.0.0-dev-00093 7 12/28/2025
4.2.1-dev-00092 16 12/12/2025
4.2.0 12 12/12/2025
4.2.0-dev-00079 9 12/14/2025
4.1.2 13 12/10/2025
4.1.2-dev-00062 12 12/30/2025
4.1.1 13 12/13/2025
4.1.1-dev-00058 14 12/11/2025
4.1.0 17 12/09/2025
4.1.0-dev-00054 11 12/11/2025
4.0.0 12 12/13/2025
4.0.0-dev-00051 14 12/14/2025
4.0.0-dev-00050 15 12/10/2025
3.1.0 16 12/10/2025
3.1.0-dev-00041 11 01/02/2026
3.1.0-dev-00037 10 12/10/2025
3.1.0-dev-00035 9 12/13/2025
3.0.0 16 12/12/2025
3.0.0-dev-00024 8 12/13/2025
3.0.0-dev-00019 16 12/11/2025
3.0.0-dev-00016 13 12/12/2025
3.0.0-dev-00015 9 12/14/2025
2.0.1-dev-00009 16 12/12/2025
2.0.1-dev-00007 11 12/19/2025
2.0.1-dev-00004 11 01/01/2026
2.0.0 12 12/11/2025
2.0.0-dev-00001 16 12/10/2025