NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
NuGet
NuGet, #2427 most downloaded on NuGet
Adds OpenTracing instrumentation for .NET Core apps that use the `Microsoft.Extensions.*` stack. Instrumented components: HttpClient calls, ASP.NET Core, Entity Framework Core and any other library that uses DiagnosticSource events.
Latest stable
0.9.0
Last release 4 years ago
no release in 18 months
Release timing varies
gaps range from 2 weeks to 1.2 years
Nearly every release is documented
notes for 12 of 12 stable releases
Nothing withdrawn
no release was ever pulled
9 years old
12 releases · first in 2018
Drag across the ruler to compare, or tap a release to open it.
Adds support for .NET 7 (thank you, @mehyaa)
added .NET 6.0 support and samples by @Aaronontheweb in #91
Full Changelog: v0.7.1...v0.8.0
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Full Changelog: https://github.com/opentracing-contrib/csharp-netcore/compare/v0.7.1...v0.8.0
This release includes the following changes:
This release includes the following changes:
GenericDiagnosticOptions.IgnoreEvent() was added again (it was removed by mistake in v0.7.0)System.Data.SqlClient no longer displays as a dependency for .NET 5.0This is one last big change for this project that should hopefully bring it in a state that fixes the most pressing issues and should therefore make i
This is one last big change for this project that should hopefully bring it in a state that fixes the most pressing issues and should therefore make it reasonably useful until OpenTelemetry is GA.
The OpenTelemetry .NET library can be found at https://github.com/open-telemetry/opentelemetry-dotnet.
*Options-types are now in the OpenTracing.Contrib.NetCore.Configuration namespace!ConfigureAspNetCore(options => options.IgnoredEvents.Clear()) if you still want to see all events. You can also just remove certain events from that list.ConfigureAspNetCore(options => options.LogEvents = false) if you don't want to have any ASP.NET Core related events added to your spans.AddAspNetCore()), all other areas are set to options.StartRootSpans = false (see below). This means that no spans are created if you ignore a request via options.IgnorePatterns.AddCoreFx() has been removed. Instead there's now separate methods for each instrumented feature:
AddHttpHandler()/ConfigureHttpHandler() for instrumenting System.Net.Http (HttpClient)AddGenericDiagnostics()/ConfigureGenericDiagnostics() for instrumenting generic DiagnosticListeners.GenericEventOptions-type has been removed.
RemoveGenericDiagnostics() instead of GenericEventOptions.IgnoreAll to completely disable the tracing of generic DiagnosticListeners.ConfigureGenericDiagnostics() to add certain IgnoredListenerNames and IgnoredEvents.System.Data.SqlClient and the newer Microsoft.Data.SqlClient. Use the corresponding AddSystemSqlClient()/ConfigureSystemSqlClient() & AddMicrosoftSqlClient()/ConfigureMicrosoftSqlClient() methods to configure the behavior.options.StartRootSpans equals true, spans for SqlClient will only be created if there is an active parent span. ASP.NET Core instrumentation enables this feature and will therefore NOT create any spans if the ASP.NET Core request itself is ignored.options.LogEvents & options.IgnoredEvents to customize if & which events should be added to the spans.ConfigureEntityFrameworkCore(options => options.IgnoredEvents.Clear()) to trace all events or modify the IgnoredEvents-list to your liking. Set options.LogEvents = false to disable all events.options.StartRootSpans equals true, spans for EF Core will only be created if there is an active parent span. ASP.NET Core instrumentation enables this feature and will therefore NOT create any spans if the ASP.NET Core request itself is ignored.Microsoft.AspNetCore has been increased to Warning to reduce the amount of span events.Remove the current Span from the HttpRequestMessage properties on System.Net.Http.HttpRequestOut.Stop
PropertyFetcher is now case-insensitive
Add ignore patterns support for MVC event processor (#35) by @d1mnewz
Enhancements
Enhancements: * #19: Assembly is now strong-named Fixes: * #23: Handling rendering of HTTP/1.0 requests without Host (by @rwkarg)
Enhancements:
Fixes:
This release now targets OpenTracing 0.12.0
This release now targets OpenTracing 0.12.0
StackOverflowException if tracer tries to resolve ILoggerFactory
StackOverflowException if tracer tries to resolve ILoggerFactory (#14)
NuGet package now uses OpenTracing logo #4
Microsoft.Extensions.Logging to tracer.ActiveSpan.Log() #7Initial release. Adds OpenTracing instrumentation for the following components:
Initial release. Adds OpenTracing instrumentation for the following components:
DiagnosticSource and Activity types (from System.Diagnostics.DiagnosticSource)This library targets netcoreapp2.0 and therefore only supports .NET Core 2.0+ based apps (ASP.NET Core and non-web based apps).
To start the instrumentation, add the package reference OpenTracing.Contrib.NetCore and call services.AddOpenTracing() in your ConfigureServices method.
Note that you need an OpenTracing compatible tracer to consume this data.
One column per quarter.