SerilogTracing 1.0.0-dev-00031

This is a prerelease version of SerilogTracing.
There is a newer version of this package available.
See the version list below for details.
dotnet add package SerilogTracing --version 1.0.0-dev-00031
NuGet\Install-Package SerilogTracing -Version 1.0.0-dev-00031
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="SerilogTracing" Version="1.0.0-dev-00031" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add SerilogTracing --version 1.0.0-dev-00031
#r "nuget: SerilogTracing, 1.0.0-dev-00031"
#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 SerilogTracing as a Cake Addin
#addin nuget:?package=SerilogTracing&version=1.0.0-dev-00031&prerelease

// Install SerilogTracing as a Cake Tool
#tool nuget:?package=SerilogTracing&version=1.0.0-dev-00031&prerelease

SerilogTracing

An experimental Serilog extension for producing and capturing hierarchical traces.

This is the logical successor to SerilogTimings, which provides very similar functionality, but emits plain log events rather than hierarchical traces.

What is SerilogTracing?

SerilogTracing integrates Serilog with the System.Diagnostics.Activity* types provided by the .NET BCL. This makes it possible to:

  1. Record traces generated using the .NET APIs through Serilog sinks, and
  2. Generate rich traces using Serilog APIs and idioms, that can still be observed by other consumers of the .NET APIs.

There are two main scenarios where these capabilities combine usefully.

First, at development time, routing trace information through Serilog means that all of the beautiful, developer-friendly Serilog outputs can be used for simple local feedback.

Here's what that looks like, routed through Serilog's console sink:

A screenshot of Windows Terminal showing output from the included Example application.

The example is using Serilog's ExpressionTemplate to annotate each span in the trace with timing information. The layout is fully configurable - check out Program.cs in the included example project - so let your ASCII artistry run wild!

Second, in production, Serilog's existing configuration, enrichment, filtering, formatting, and output facilities can potentially provide a flexible mechanism for emitting trace data to a wide range of targets.

Notably, any system that accepts traces in text or JSON format should be an easy target for SerilogTracing and a Serilog sink; here's Seq showing traces delivered using the production Serilog.Sinks.Seq package and a custom ITextFormatter implemented with ExpressionTemplate:

A screenshot of Seq showing output from the included Example application.

How does it work?

And what do we mean by "tracing"?

A trace is just a collection of spans, and a span is just an event that carries a:

  • trace id,
  • span id,
  • parent span id (optional),
  • start time, and
  • duration.

SerilogTracing generates spans using extension methods on ILogger:

using var activity = logger.StartActivity("Compute {A} + {B}", a, b);
// ... on `Dispose()` the activity will be recorded as a span

The spans generated by SerilogTracing are converted into Serilog LogEvents and routed through the logger. There's nothing particularly special about these events, except that they add ParentSpanId and SpanStartTimestamp properties to represent the parts of a span not already covered by the other parts of the LogEvent.

SerilogTracing needs to hook into the logging pipeline at creation time; currently this must be done using:

Log.Logger = new LoggerConfiguration()
    ... // Other configuration as usual, then:
    .CreateTracingLogger();

In addition to generating spans, SerilogTracing also consumes spans generated elsewhere in an application via the System.Diagnostics.Activity APIs, such as those produced by ASP.NET Core or HttpClient. Activity sources can be enabled or disabled using the logger's MinimumLevel.Override settings.

Finally, SerilogTracing includes some examples showing how the resulting LogEvents can be formatted for various trace-aware outputs.

Starting, enriching, and completing activities

Activities are represented by LoggerActivity instances.

LoggerActivity has a simple lifetime:

  • The activity is started using one of the ILogger.StartActivity() extensions,
  • Properties are added to the activity using LoggerActivity.AddProperty(), and
  • The activity is completed either implicitly, by IDisposable.Dispose(), or explicitly using LoggerActivity.Complete().

LoggerActivity.Complete() accepts optional LogEventLevel and Exception arguments.

Displaying output

Use the formatters provides by Serilog.Tracing.Formatting.DefaultFormatting to pretty-print spans as text, or serialize to JSON.

Configuring the activity listener

Activity sources can be enabled and disabled using the standard MinimumLevel.Override() mechanism.

Status

This project is experimental. It's not a part of Serilog, not maintained by the Serilog maintainers, and might not evolve in any particular way: there's currently no plan to integrate this functionality directly into Serilog. (Having said that, this project is a vehicle to explore those possibilities).

Product Compatible and additional computed target framework versions.
.NET 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 was computed.  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. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (7)

Showing the top 5 NuGet packages that depend on SerilogTracing:

Package Downloads
SerilogTracing.Instrumentation.AspNetCore

Package Description

SerilogTracing.Expressions

Package Description

SerilogTracing.Sinks.OpenTelemetry

Sends log events and traces to OTLP (gRPC or HTTP) endpoints.

SerilogTracing.Instrumentation.SqlClient

Package Description

SerilogTracing.Sinks.Seq

Package Description

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
2.0.0 13,927 6/4/2024
2.0.0-dev-00306 147 6/3/2024
2.0.0-dev-00305 171 6/3/2024
2.0.0-dev-00304 158 6/1/2024
2.0.0-dev-00303 162 6/1/2024
1.1.0 14,189 5/2/2024
1.1.0-dev-00298 143 5/24/2024
1.1.0-dev-00297 141 5/24/2024
1.1.0-dev-00296 149 5/24/2024
1.1.0-dev-00295 115 5/16/2024
1.1.0-dev-00292 171 5/10/2024
1.1.0-dev-00287 180 5/1/2024
1.1.0-dev-00286 179 5/1/2024
1.1.0-dev-00283 167 4/30/2024
1.1.0-dev-00282 176 4/30/2024
1.0.1 8,464 4/18/2024
1.0.1-dev-00280 177 4/30/2024
1.0.1-dev-00276 144 4/18/2024
1.0.1-dev-00275 144 4/18/2024
1.0.1-dev-00273 8,341 3/26/2024
1.0.1-dev-00267 33,098 3/11/2024
1.0.1-dev-00266 262 3/11/2024
1.0.1-dev-00264 170 3/10/2024
1.0.1-dev-00261 756 3/5/2024
1.0.0 15,115 3/3/2024
1.0.0-dev-00257 2,950 2/29/2024
1.0.0-dev-00256 152 2/29/2024
1.0.0-dev-00251 511 2/27/2024
1.0.0-dev-00249 150 2/26/2024
1.0.0-dev-00247 164 2/26/2024
1.0.0-dev-00246 158 2/24/2024
1.0.0-dev-00242 1,251 2/22/2024
1.0.0-dev-00240 164 2/21/2024
1.0.0-dev-00236 161 2/21/2024
1.0.0-dev-00233 1,810 2/12/2024
1.0.0-dev-00231 480 2/12/2024
1.0.0-dev-00229 131 2/12/2024
1.0.0-dev-00228 150 2/12/2024
1.0.0-dev-00227 149 2/12/2024
1.0.0-dev-00225 142 2/12/2024
1.0.0-dev-00214 569 2/10/2024
1.0.0-dev-00179 152 2/9/2024
1.0.0-dev-00167 120 2/8/2024
1.0.0-dev-00164 146 2/8/2024
1.0.0-dev-00159 129 2/8/2024
1.0.0-dev-00155 162 2/7/2024
1.0.0-dev-00150 114 2/7/2024
1.0.0-dev-00142 230 2/6/2024
1.0.0-dev-00138 138 2/6/2024
1.0.0-dev-00135 151 2/6/2024
1.0.0-dev-00134 138 2/6/2024
1.0.0-dev-00132 179 2/5/2024
1.0.0-dev-00127 130 2/5/2024
1.0.0-dev-00121 164 2/1/2024
1.0.0-dev-00118 141 2/1/2024
1.0.0-dev-00115 144 2/1/2024
1.0.0-dev-00113 146 2/1/2024
1.0.0-dev-00107 122 1/31/2024
1.0.0-dev-00103 167 1/30/2024
1.0.0-dev-00102 1,054 1/25/2024
1.0.0-dev-00100 319 1/24/2024
1.0.0-dev-00097 131 1/24/2024
1.0.0-dev-00090 292 1/24/2024
1.0.0-dev-00088 993 1/22/2024
1.0.0-dev-00087 143 1/19/2024
1.0.0-dev-00086 99 1/18/2024
1.0.0-dev-00082 111 1/17/2024
1.0.0-dev-00080 112 1/17/2024
1.0.0-dev-00079 111 1/17/2024
1.0.0-dev-00077 107 1/17/2024
1.0.0-dev-00076 107 1/17/2024
1.0.0-dev-00070 106 1/16/2024
1.0.0-dev-00067 112 1/16/2024
1.0.0-dev-00066 108 1/16/2024
1.0.0-dev-00055 224 1/11/2024
1.0.0-dev-00051 95 1/10/2024
1.0.0-dev-00049 88 1/9/2024
1.0.0-dev-00044 90 1/9/2024
1.0.0-dev-00039 151 1/4/2024
1.0.0-dev-00038 77 1/4/2024
1.0.0-dev-00037 84 1/3/2024
1.0.0-dev-00034 77 1/3/2024
1.0.0-dev-00031 79 1/2/2024
1.0.0-dev-00030 83 1/2/2024
1.0.0-dev-00022 589 12/4/2023
1.0.0-dev-00017 96 11/28/2023
1.0.0-dev-00016 127 11/15/2023
1.0.0-dev-00015 80 11/15/2023
1.0.0-dev-00011 87 11/10/2023
1.0.0-dev-00010 576 11/7/2023
1.0.0-dev-00009 68 11/5/2023