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
17
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
18
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
23
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
54
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
158

Version Downloads Last updated
9.0.1-dev-02307 7 02/27/2025
9.0.0 8 12/21/2024
9.0.0-dev-02303 8 12/05/2024
9.0.0-dev-02301 9 12/03/2024
8.0.0 185 04/23/2024
8.0.0-dev-00145 17 05/30/2024
8.0.0-dev-00143 21 05/30/2024
8.0.0-dev-00140 19 05/30/2024
8.0.0-dev-00137 21 04/26/2024
7.0.0 15 06/07/2023
7.0.0-dev-00131 16 05/30/2024
7.0.0-dev-00129 16 04/29/2024
7.0.0-dev-00126 13 11/07/2024
5.1.0-dev-00123 25 04/25/2024
5.0.1 58 12/14/2022
5.0.1-dev-00113 11 11/28/2024
5.0.0 17 05/23/2024
5.0.0-dev-00108 20 04/26/2024
5.0.0-dev-00095 15 05/05/2022
5.0.0-dev-00094 22 05/30/2024
5.0.0-dev-00093 17 05/17/2024
4.2.1-dev-00092 19 05/30/2024
4.2.0 13,839 04/14/2022
4.2.0-dev-00079 17 05/16/2024
4.1.2 171 04/25/2022
4.1.2-dev-00062 13 05/30/2024
4.1.1 15 04/30/2024
4.1.1-dev-00058 18 04/26/2024
4.1.0 19 05/07/2022
4.1.0-dev-00054 17 04/26/2024
4.0.0 15 04/26/2024
4.0.0-dev-00051 17 04/26/2024
4.0.0-dev-00050 20 04/26/2024
3.1.0 26 04/26/2024
3.1.0-dev-00041 11 11/14/2024
3.1.0-dev-00037 21 05/30/2024
3.1.0-dev-00035 17 05/22/2024
3.0.0 22 05/09/2024
3.0.0-dev-00024 23 05/30/2024
3.0.0-dev-00019 18 05/12/2024
3.0.0-dev-00016 25 05/05/2022
3.0.0-dev-00015 16 04/26/2024
2.0.1-dev-00009 11 05/30/2024
2.0.1-dev-00007 15 04/29/2024
2.0.1-dev-00004 18 04/26/2024
2.0.0 17 05/22/2024
2.0.0-dev-00001 20 04/26/2022