Note: NuGet packages are no longer required to enable automatic instrumentation in .NET Core or to enable the ASP.NET instrumentation in .NET Framework. If you are using NuGet packages Datadog.Trace.AspNet or Datadog.Trace.ClrProfiler.Managed, you may remove them from your application when you update the .NET Tracer. We will publish updated packages that are empty (no assemblies) for backwards compatibility, but these are now DEPRECATED.
NuGet package Datadog.Trace is still used for manual instrumentation or to configure the Tracer in code. Please keep the NuGet package version in sync with the installed Tracer if you will be mixing automatic and manual instrumentation in the same application.
Note: In these release notes and in the .NET Tracer documentation, "ASP.NET" refers to the legacy web framework included in .NET Framework, and "ASP.NET Core" refers to the modern open-source cross-platform web framework used in .NET Core.
New
- ASP.NET instrumentation is now enabled automatically (#610)
- add support for ASP.NET Web API 5.1 (#605)
- add support for ASP.NET Core apps that do not use MVC (#611, ...)
- add global sample rate configuration setting
DD_TRACE_SAMPLE_RATE(#607)
Fixed
- rewrite ASP.NET Core instrumentation to use built-in telemetry (#611, #626, #628, #629)
- fix issue with missing traces in ASP.NET Core 3.1
- fix issue with http status code 500 not flagged as error
- standardize sampling rules and rate limiter configuration between different language Tracers (#598)
- fix
System.EntryPointNotFoundException: Entry point was not foundin MongoDb integration (#566) - improve WCF resource names (#602)
- update spans after unhandled exceptions in ASP.NET Web API 2 (#604)
- fix synchronization of active scope in ASP.NET (#612)
- prevent unhandled
SecurityExceptionin logging code (#613) - fix
NullReferenceExceptionwhen injecting trace ID with NLog 1.0.0.505 - fix integration name used to configure
SqlCommandIntegration(#622)