Serilog.Extensions.Hosting 8.0.0-dev-00137

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,200
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
212
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
27
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
26
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
25
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
23
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
22

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