Serilog.Extensions.Logging 8.0.0

The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org. Prefix Reserved
There is a newer prerelease version of this package available.
See the version list below for details.
dotnet add package Serilog.Extensions.Logging --version 8.0.0
NuGet\Install-Package Serilog.Extensions.Logging -Version 8.0.0
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Serilog.Extensions.Logging" Version="8.0.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Serilog.Extensions.Logging --version 8.0.0
#r "nuget: Serilog.Extensions.Logging, 8.0.0"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Serilog.Extensions.Logging as a Cake Addin
#addin nuget:?package=Serilog.Extensions.Logging&version=8.0.0

// Install Serilog.Extensions.Logging as a Cake Tool
#tool nuget:?package=Serilog.Extensions.Logging&version=8.0.0

Serilog.Extensions.Logging Build status NuGet Version

A Serilog provider for Microsoft.Extensions.Logging, the logging subsystem used by ASP.NET Core.

ASP.NET Core Instructions

ASP.NET Core applications should prefer Serilog.AspNetCore and UseSerilog() instead.

Non-web .NET Core Instructions

Non-web .NET Core applications should prefer Serilog.Extensions.Hosting and UseSerilog() instead.

.NET Core 1.0, 1.1 and Default Provider Integration

The package implements AddSerilog() on ILoggingBuilder and ILoggerFactory to enable the Serilog provider under the default Microsoft.Extensions.Logging implementation.

First, install the Serilog.Extensions.Logging NuGet package into your web or console app. You will need a way to view the log messages - Serilog.Sinks.Console writes these to the console.

dotnet add package Serilog.Extensions.Logging
dotnet add package Serilog.Sinks.Console

Next, in your application's Startup method, configure Serilog first:

using Serilog;

public class Startup
{
  public Startup(IHostingEnvironment env)
  {
    Log.Logger = new LoggerConfiguration()
      .Enrich.FromLogContext()
      .WriteTo.Console()
      .CreateLogger();

    // Other startup code

Finally, for .NET Core 2.0+, in your Startup class's Configure() method, remove the existing logger configuration entries and call AddSerilog() on the provided loggingBuilder.

  public void ConfigureServices(IServiceCollection services)
  {
      services.AddLogging(loggingBuilder =>
      	loggingBuilder.AddSerilog(dispose: true));

      // Other services ...
  }

For .NET Core 1.0 or 1.1, in your Startup class's Configure() method, remove the existing logger configuration entries and call AddSerilog() on the provided loggerFactory.

  public void Configure(IApplicationBuilder app,
                        IHostingEnvironment env,
                        ILoggerFactory loggerfactory,
                        IApplicationLifetime appLifetime)
  {
      loggerfactory.AddSerilog();

      // Ensure any buffered events are sent at shutdown
      appLifetime.ApplicationStopped.Register(Log.CloseAndFlush);

That's it! With the level bumped up a little you should see log output like:

[22:14:44.646 DBG] RouteCollection.RouteAsync
	Routes:
		Microsoft.AspNet.Mvc.Routing.AttributeRoute
		{controller=Home}/{action=Index}/{id?}
	Handled? True
[22:14:44.647 DBG] RouterMiddleware.Invoke
	Handled? True
[22:14:45.706 DBG] /lib/jquery/jquery.js not modified
[22:14:45.706 DBG] /css/site.css not modified
[22:14:45.741 DBG] Handled. Status code: 304 File: /css/site.css

Notes on Log Scopes

Microsoft.Extensions.Logging provides the BeginScope API, which can be used to add arbitrary properties to log events within a certain region of code. The API comes in two forms:

  1. The method: IDisposable BeginScope<TState>(TState state)
  2. The extension method: IDisposable BeginScope(this ILogger logger, string messageFormat, params object[] args)

Using the extension method will add a Scope property to your log events. This is most useful for adding simple "scope strings" to your events, as in the following code:

using (_logger.BeginScope("Transaction")) {
    _logger.LogInformation("Beginning...");
    _logger.LogInformation("Completed in {DurationMs}ms...", 30);
}
// Example JSON output:
// {"@t":"2020-10-29T19:05:56.4126822Z","@m":"Beginning...","@i":"f6a328e9","SourceContext":"SomeNamespace.SomeService","Scope":["Transaction"]}
// {"@t":"2020-10-29T19:05:56.4176816Z","@m":"Completed in 30ms...","@i":"51812baa","DurationMs":30,"SourceContext":"SomeNamespace.SomeService","Scope":["Transaction"]}

If you simply want to add a "bag" of additional properties to your log events, however, this extension method approach can be overly verbose. For example, to add TransactionId and ResponseJson properties to your log events, you would have to do something like the following:

// WRONG! Prefer the dictionary approach below instead
using (_logger.BeginScope("TransactionId: {TransactionId}, ResponseJson: {ResponseJson}", 12345, jsonString)) {
    _logger.LogInformation("Completed in {DurationMs}ms...", 30);
}
// Example JSON output:
// {
//	"@t":"2020-10-29T19:05:56.4176816Z",
//	"@m":"Completed in 30ms...",
//	"@i":"51812baa",
//	"DurationMs":30,
//	"SourceContext":"SomeNamespace.SomeService",
//	"TransactionId": 12345,
//	"ResponseJson": "{ \"Key1\": \"Value1\", \"Key2\": \"Value2\" }",
//	"Scope":["TransactionId: 12345, ResponseJson: { \"Key1\": \"Value1\", \"Key2\": \"Value2\" }"]
// }

Not only does this add the unnecessary Scope property to your event, but it also duplicates serialized values between Scope and the intended properties, as you can see here with ResponseJson. If this were "real" JSON like an API response, then a potentially very large block of text would be duplicated within your log event! Moreover, the template string within BeginScope is rather arbitrary when all you want to do is add a bag of properties, and you start mixing enriching concerns with formatting concerns.

A far better alternative is to use the BeginScope<TState>(TState state) method. If you provide any IEnumerable<KeyValuePair<string, object>> to this method, then Serilog will output the key/value pairs as structured properties without the Scope property, as in this example:

var scopeProps = new Dictionary<string, object> {
    { "TransactionId", 12345 },
    { "ResponseJson", jsonString },
};
using (_logger.BeginScope(scopeProps) {
    _logger.LogInformation("Transaction completed in {DurationMs}ms...", 30);
}
// Example JSON output:
// {
//	"@t":"2020-10-29T19:05:56.4176816Z",
//	"@m":"Completed in 30ms...",
//	"@i":"51812baa",
//	"DurationMs":30,
//	"SourceContext":"SomeNamespace.SomeService",
//	"TransactionId": 12345,
//	"ResponseJson": "{ \"Key1\": \"Value1\", \"Key2\": \"Value2\" }"
// }

Versioning

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

Credits

This package evolved from an earlier package Microsoft.Framework.Logging.Serilog provided by the ASP.NET team.

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 is compatible.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 is compatible.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 is compatible. 
.NET Framework net461 was computed.  net462 is compatible.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (594)

Showing the top 5 NuGet packages that depend on Serilog.Extensions.Logging:

Package Downloads
Serilog.Extensions.Hosting The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org.

Serilog support for .NET Core logging in hosted services

Serilog.AspNetCore The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org.

Serilog support for ASP.NET Core logging

Serilog.Extensions.Logging.File The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org.

Add file logging to ASP.NET Core apps with one line of code.

Pulumi

The Pulumi .NET SDK lets you write cloud programs in C#, F#, and VB.NET.

IppDotNetSdkForQuickBooksApiV3

The IPP .NET SDK for QuickBooks V3 is a set of .NET classes that make it easier to call QuickBooks APIs. This is the .Net Standard 2.0 version of the .Net SDK

GitHub repositories (181)

Showing the top 5 popular GitHub repositories that depend on Serilog.Extensions.Logging:

Repository Stars
bitwarden/server
The core infrastructure backend (API, database, Docker, etc).
abpframework/abp
Open Source Web Application Framework for ASP.NET Core. Offers an opinionated architecture to build enterprise software solutions with best practices on top of the .NET and the ASP.NET Core platforms. Provides the fundamental infrastructure, production-ready startup templates, application modules, UI themes, tooling, guides and documentation.
IdentityServer/IdentityServer4
OpenID Connect and OAuth 2.0 Framework for ASP.NET Core
spectreconsole/spectre.console
A .NET library that makes it easier to create beautiful console applications.
microsoft/reverse-proxy
A toolkit for developing high-performance HTTP reverse proxy applications.
Version Downloads Last updated
8.0.1-dev-10382 288 3/14/2024
8.0.1-dev-10377 2,327 2/22/2024
8.0.1-dev-10373 1,004 2/14/2024
8.0.1-dev-10370 33,689 11/14/2023
8.0.0 8,717,074 11/14/2023
8.0.0-dev-10367 483 11/14/2023
8.0.0-dev-10359 6,846 10/23/2023
7.0.1-dev-10354 52,470 10/10/2023
7.0.0 24,273,409 5/10/2023
7.0.0-dev-10353 637 10/3/2023
7.0.0-dev-10346 8,545 5/4/2023
3.1.1-dev-10338 29,257 3/13/2023
3.1.1-dev-10337 840 3/13/2023
3.1.1-dev-10301 280,952 4/7/2022
3.1.0 136,025,575 11/1/2021
3.1.0-dev-10295 1,098 11/1/2021
3.0.2-dev-10289 140,353 5/17/2021
3.0.2-dev-10286 8,535 5/6/2021
3.0.2-dev-10284 2,728,295 1/8/2021
3.0.2-dev-10281 305,681 8/2/2020
3.0.2-dev-10280 122,710 5/14/2020
3.0.2-dev-10272 97,090 3/2/2020
3.0.2-dev-10269 15,947 2/24/2020
3.0.2-dev-10265 170,189 12/11/2019
3.0.2-dev-10260 76,156 10/4/2019
3.0.2-dev-10257 55,940 9/20/2019
3.0.2-dev-10256 23,448 9/3/2019
3.0.1 186,709,680 8/21/2019
3.0.1-dev-10252 1,368 8/21/2019
3.0.0 221,147 8/20/2019
3.0.0-dev-10248 2,397 8/20/2019
3.0.0-dev-10244 1,538 8/19/2019
3.0.0-dev-10240 165,916 5/21/2019
3.0.0-dev-10237 1,679 5/21/2019
3.0.0-dev-10234 1,367 5/21/2019
3.0.0-dev-10232 1,407 5/21/2019
2.0.5-dev-10226 5,474 5/2/2019
2.0.5-dev-10225 1,448 5/2/2019
2.0.4 6,192,277 4/23/2019
2.0.3 189,581 4/23/2019
2.0.3-dev-10220 1,493 4/23/2019
2.0.3-dev-10215 1,357 4/23/2019
2.0.2 25,121,038 8/28/2017
2.0.2-dev-10199 1,720 8/28/2017
2.0.1 18,739 8/28/2017
2.0.1-dev-10207 1,556 9/22/2018
2.0.1-dev-10205 1,803 5/9/2018
2.0.1-dev-10204 1,881 1/17/2018
2.0.1-dev-10195 1,693 8/28/2017
2.0.0 26,294,916 8/18/2017
2.0.0-dev-10187 1,736 8/24/2017
2.0.0-dev-10185 1,702 8/23/2017
2.0.0-dev-10180 2,059 8/17/2017
2.0.0-dev-10177 1,827 8/16/2017
2.0.0-dev-10174 2,169 8/15/2017
2.0.0-dev-10172 17,123 7/31/2017
2.0.0-dev-10169 7,942 7/18/2017
2.0.0-dev-10164 2,006 7/17/2017
1.4.1-dev-10155 27,090 4/22/2017
1.4.1-dev-10152 1,717 4/22/2017
1.4.1-dev-10147 37,980 2/15/2017
1.4.0 6,356,294 2/14/2017
1.4.0-dev-10144 1,765 2/14/2017
1.4.0-dev-10138 121,088 1/16/2017
1.4.0-dev-10136 15,931 11/18/2016
1.4.0-dev-10133 2,017 11/16/2016
1.3.1 886,552 11/18/2016
1.3.0 13,225 11/16/2016
1.3.0-dev-10129 3,651 11/15/2016
1.3.0-dev-10125 23,657 8/21/2016
1.2.0 731,279 8/8/2016
1.2.0-dev-10122 2,410 8/3/2016
1.1.0 34,918 7/26/2016
1.1.0-dev-10116 5,950 7/15/2016
1.1.0-dev-10114 1,946 7/14/2016
1.0.0 385,211 6/27/2016
1.0.0-rc2-10110 8,083 5/29/2016
1.0.0-rc2-10108 1,792 5/28/2016
1.0.0-rc2-10104 4,311 5/19/2016
1.0.0-rc2-10102 1,760 5/18/2016
1.0.0-rc2-10099 2,121 5/18/2016
1.0.0-rc2-10096 2,012 5/17/2016
1.0.0-rc1-final-10092 16,419 1/26/2016
1.0.0-rc1-final-10091 1,799 1/26/2016
1.0.0-rc1-final-10088 1,832 1/26/2016
1.0.0-rc1-final-10087 1,722 1/26/2016
1.0.0-rc1-final-10086 2,460 1/26/2016