Datadog.Trace
3.0.0-prerelease
Prefix Reserved
See the version list below for details.
dotnet add package Datadog.Trace --version 3.0.0-prerelease
NuGet\Install-Package Datadog.Trace -Version 3.0.0-prerelease
<PackageReference Include="Datadog.Trace" Version="3.0.0-prerelease" />
paket add Datadog.Trace --version 3.0.0-prerelease
#r "nuget: Datadog.Trace, 3.0.0-prerelease"
// Install Datadog.Trace as a Cake Addin #addin nuget:?package=Datadog.Trace&version=3.0.0-prerelease&prerelease // Install Datadog.Trace as a Cake Tool #tool nuget:?package=Datadog.Trace&version=3.0.0-prerelease&prerelease
Datadog.Trace NuGet package
This package contains the Datadog .NET APM tracer for configuring custom instrumentation.
If you are only using automatic instrumentation, you do not need this package. Please read our documentation for details on how to install the tracer for automatic instrumentation.
If you are using automatic instrumentation and would like to interact with APM only through C# attributes, see the Datadog.Trace.Annotations NuGet package.
Please note that Datadog does not support tracing (manual or automatic) in partial-trust environments.
Getting Started
- Configure the Datadog agent for APM as described in our documentation.
- For automatic instrumentation, install and enable the tracer as described in our documentation.
- Configure custom instrumentation, as shown below
- View your live data on Datadog.
Configuring Datadog in code
There are multiple ways to configure your application: using environment variables, a web.config
file, or a datadog.json
file, as described in our documentation. This NuGet package also allows you to configure settings in code.
To override configuration settings, create an instance of TracerSettings
, and pass it to the static Tracer.Configure()
method:
using Datadog.Trace;
// Create a settings object using the existing
// environment variables and config sources
var settings = TracerSettings.FromDefaultSources();
// Override a value
settings.GlobalTags.Add("SomeKey", "SomeValue");
// Replace the tracer configuration
Tracer.Configure(settings);
Calling Tracer.Configure()
will replace the settings for all subsequent traces, both for custom instrumentation and for automatic instrumentation.
⚠️ Replacing the configuration should be done once, as early as possible in your application.
Create custom traces
To create and activate a custom span, use Tracer.Instance.StartActive()
. If a trace is already active (when created by automatic instrumentation, for example), the span will be part of the current trace. If there is no current trace, a new one will be started.
⚠️ Ensure you dispose of the scope returned from StartActive. Disposing the scope will close the span, and ensure the trace is flushed to Datadog once all its spans are closed.
using Datadog.Trace;
// Start a new span
using (var scope = Tracer.Instance.StartActive("custom-operation"))
{
// Do something
}
Release Notes
You can view the notes for the latest release on GitHub.
Upgrading from 1.x to 2.0
.NET Tracer 2.0 introduces several breaking changes to the API which allow various performance improvements, add new features, and deprecate problematic ways of using the package. Most of these changes do not require any changes to your code, but some patterns are no longer supported or recommended.
This section describes some of the most important breaking changes. For full details see the release notes on GitHub.
Supported .NET versions
.NET Tracer 2.0 adds support for .NET 6.0 and raises the minimum supported version of .NET Framework from .NET Framework 4.5 to .NET Framework 4.6.1. If you are currently targeting version < 4.6.1, we suggest you upgrade in line with Microsoft's guidance.
For full details of supported versions, see our documentation on .NET Framework compatibility requirements and .NET/.NET Core compatibility requirements.
Note that Datadog does not support tracing (manual or automatic) in partial-trust environments.
Singleton Tracer
instances
In .NET Tracer 1.x, you could create new Tracer
instances with different settings for each instance, using the Tracer
constructor. In .NET Tracer 2.0 this constructor is marked [Obsolete]
and it is no longer possible to create Tracer
instances with different settings. This was done to avoid multiple problematic patterns that were hard for users to detect.
To update your code:
using Datadog.Trace;
// Create your settings as before
var settings = new TracerSettings();
// var tracer = new Tracer(settings) // <- Delete this line
Tracer.Configure(settings); // <- Add this line
Immutable Tracer.Settings
In .NET Tracer 1.x the TracerSettings
object passed into a Tracer
instance could be modified later. Depending on the changes, the tracer may or may not respect the changes. In .NET Tracer 2.0, an ImmutableTracerSettings
object is created when the Tracer
instance is configured. The property Tracer.Settings
now returns ImmutableTracerSettings
, not TracerSettings
. Subsequent changes to the original TracerSettings
instance will not be observed by Tracer
.
To update your code:
using Datadog.Trace;
var settings = TracerSettings.FromDefaultSources();
settings.TraceEnabled = false; // TracerSettings are mutable
Tracer.Configure(settings);
// All properties on Tracer.Settings are now read-only
// Tracer.Instance.Settings.TraceEnabled = false; // <- DOES NOT COMPILE
Exporter settings
Exporter-related settings were grouped into the TracerSettings.Exporter
property.
To update your code:
using Datadog.Trace;
var settings = TracerSettings.FromDefaultSources();
// settings.AgentUri = "http://localhost:8126"; // <- Delete this line
settings.Exporter.AgentUri = "http://localhost:8126"; // <- Add this line
Tracer.Configure(settings);
Configure ADO.NET integrations individually
In .NET Tracer 1.x, you could configure automatic instrumentation of all ADO.NET integrations using the AdoNet
integration ID. In .NET Tracer 2.0, you can now configure specific integrations using the following integration IDs:
MySql
Npgsql
(PostgreSQL)Oracle
SqlClient
(SQL Server)Sqlite
See our documentation for a complete list of supported integration IDs. Note that you can still disable all ADO.NET integrations using the AdoNet
integration ID.
This change also removes the now-obsolete TracerSettings.AdoNetExcludedTypes
setting and the corresponding environment variable DD_TRACE_ADONET_EXCLUDED_TYPES
. Replace usages of these with TracerSettings.Integrations["<INTEGRATION_NAME>"].Enabled
and DD_TRACE_<INTEGRATION_NAME>_ENABLED
, respectively:
using Datadog.Trace;
var settings = TracerSettings.FromDefaultSources();
// settings.AdoNetExcludedTypes.Add("MySql"); // <- Delete this line
settings.Integrations["MySql"].Enabled = false; // <- Add this line
ElasticsearchNet5
integration ID removed
In .NET Tracer 1.x, the integration ID for version 5.x of Elasticsearch.Net
was ElasticsearchNet5
, and the integration ID for versions 6 and above was ElasticsearchNet
. In .NET Tracer 2.0, ElasticsearchNet5
was removed. Use ElasticsearchNet
for all versions of Elasticsearch.Net
.
To update your code:
using Datadog.Trace;
var settings = TracerSettings.FromDefaultSources();
settings.Integrations["ElasticsearchNet5"].Enabled = false; // <- Delete this line
settings.Integrations["ElasticsearchNet"].Enabled = false; // <- Add this line
Obsolete APIs have been removed
The following deprecated APIs were removed.
TracerSettings.DebugEnabled
was removed. Set theDD_TRACE_DEBUG
environment variable to1
to enable debug mode.Tags.ForceDrop
andTags.ForceKeep
were removed. UseTags.ManualDrop
andTags.ManualKeep
respectively instead.SpanTypes
associated with automatic instrumentation spans, such asMongoDb
andRedis
, were removed.Tags
associated with automatic instrumentation spans, such asAmqpCommand
andCosmosDbContainer
, were removed.Tracer.Create()
was removed. UseTracer.Configure()
instead.TracerSettings.AdoNetExcludedTypes
was removed. UseTracerSettings.Integrations
to configure ADO.NET automatic instrumentation.- Various internal APIs not intended for public consumption were removed.
In addition, some settings were marked obsolete in 2.0:
- Environment variables
DD_TRACE_ANALYTICS_ENABLED
,DD_TRACE_{0}_ANALYTICS_ENABLED
, andDD_TRACE_{0}_ANALYTICS_SAMPLE_RATE
for controlling App Analytics are obsolete. App Analytics has been replaced with Tracing Without Limits. See our documentation for details. TracerSettings.AnalyticsEnabled
,IntegrationSettings.AnalyticsEnabled
, andIntegrationSettings.AnalyticsSampleRate
were marked obsolete.- Environment variable
DD_TRACE_LOG_PATH
is deprecated. UseDD_TRACE_LOG_DIRECTORY
instead.
Introduction of interfaces ISpan
, IScope
, and ITracer
.NET Tracer 2.0 makes the public Scope
and Span
classes internal. Instead, we now expose public IScope
and ISpan
interfaces and the tracer API was updated accordingly. If you are currently using explicit types (instead of inferring types with var
), replace usages of Scope
with IScope
and Span
with ISpan
.
This Tracer release also adds the new ITracer
interface, implemented by the Tracer
class. The type of static property Tracer.Instance
is still Tracer
, so use of ITracer
is not required, but the new interface can be useful for testing with mocks and dependency injection.
To update your Scope/Span
code:
using Datadog.Trace;
// No changes required here (using var)
using (var scope = Tracer.Instance.StartActive("my-operation"))
{
var span = scope.Span;
// ...
}
// No longer compiles (Scope and Span are no longer public)
using (Scope scope = Tracer.Instance.StartActive("my-operation"))
{
Span span = scope.Span;
// ...
}
// Correct usage with explicit types (using IScope and ISpan)
using (IScope scope = Tracer.Instance.StartActive("my-operation"))
{
ISpan span = scope.Span;
// ...
}
Simplification of the tracer interface
In addition to returning IScope
, several parameters parameters in the Tracer.StartActive
method signature were replaced with a single SpanCreationSettings
. The span's service name can no longer be set from Tracer.StartActive
. Instead, set Span.ServiceName
after creating the span.
To update your Scope/Span
code:
using Datadog.Trace;
// No changes required here (using only operation name)
using (var scope = Tracer.Instance.StartActive("my-operation"))
{
// ...
}
// No longer compiles (most parameters removed)
using (var scope = Tracer.Instance.StartActive("my-operation", parent: spanContext, serviceName: "my-service", ...))
{
// ...
}
// Correct usage
var spanCreationSettings = new SpanCreationSettings() { Parent = spanContext };
using (var scope = Tracer.Instance.StartActive("my-operation", spanCreationSettings))
{
scope.Span.ServiceName = "my-service";
// ...
}
Incorrect integration names are ignored
In .NET Tracer 2.0, any changes made to an IntegrationSettings
object for an unknown IntegrationId
will not be persisted. Instead, a warning will be logged describing the invalid access.
using Datadog.Trace;
var tracerSettings = TracerSettings.FromDefaultSources();
// Accessing settings for an unknown integration will log a warning
var settings = tracerSettings.Integrations["MyRandomIntegration"];
// changes are not persisted
settings.Enabled = false;
// isEnabled is null, not false
bool? isEnabled = tracerSettings.Integrations["MyRandomIntegration"].Enabled;
Automatic instrumentation changes
DD_TRACE_ROUTE_TEMPLATE_RESOURCE_NAMES_ENABLED
enabled by default
.NET Tracer 1.26.0 added the DD_TRACE_ROUTE_TEMPLATE_RESOURCE_NAMES_ENABLED
feature flag, which enables improved span names for ASP.NET and ASP.NET Core automatic instrumentation spans, an additional span for ASP.NET Core requests, and additional tags.
In .NET Tracer 2.0, DD_TRACE_ROUTE_TEMPLATE_RESOURCE_NAMES_ENABLED
is enabled by default. Due to the change in span names, you may need to update your monitors and dashboards to use the new resource names.
If you do not wish to take advantage of the improved route names, you can disable the feature by setting the DD_TRACE_ROUTE_TEMPLATE_RESOURCE_NAMES_ENABLED
environment variable to 0
.
Call-site instrumentation removed
Call-site automatic instrumentation was removed in .NET Tracer 2.0 and replaced with call-target instrumentation. This was the default mode since version 1.28.0 on .NET Framework 4.6 or above and .NET Core / .NET 5. Call-target instrumentation provides performance and reliability improvements over call-site instrumentation.
Note: Call-target instrumentation does not support instrumenting custom implementations of DbCommand
yet. If you find ADO.NET spans are missing from your traces after upgrading, please raise an issue on GitHub, or contact support.
DD_INTEGRATIONS
environment variable no longer needed
The integrations.json
file is no longer required for instrumentation. You can remove references to this file, for example by deleting the DD_INTEGRATIONS
environment variable.
User Identification
The tracer provides a convenient method to link an actor to a trace. You have to pass a UserDetails
object with at least its Id property set to a non-null value.
To correlate users to web requests, you would need to use the following code snippet within each web request, after user authorization has been performed:
using Datadog.Trace;
// ...
var userDetails = new UserDetails()
{
// the systems internal identifier for the users
Id = "d41452f2-483d-4082-8728-171a3570e930",
// the email address of the user
Email = "test@adventure-works.com",
// the user's name, as displayed by the system
Name = "Jane Doh",
// the user's session id
SessionId = "d0632156-132b-4baa-95b2-a492c5f9cb16",
// the role the user is making the request under
Role = "standard",
};
Tracer.Instance.ActiveScope?.Span.SetUser(userDetails);
Get in touch
If you have questions, feedback, or feature requests, reach our support.
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. 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 was computed. 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 is compatible. |
.NET Standard | netstandard2.0 is compatible. netstandard2.1 was computed. |
.NET Framework | net461 is compatible. net462 was computed. 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. |
-
.NETCoreApp 3.1
- System.Diagnostics.DiagnosticSource (>= 4.4.1)
-
.NETFramework 4.6.1
- No dependencies.
-
.NETStandard 2.0
- System.Diagnostics.DiagnosticSource (>= 4.4.1)
- System.Reflection.Emit (>= 4.3.0)
- System.Reflection.Emit.Lightweight (>= 4.3.0)
NuGet packages (11)
Showing the top 5 NuGet packages that depend on Datadog.Trace:
Package | Downloads |
---|---|
Datadog.Trace.Bundle
Auto-instrumentation assets for Datadog APM |
|
Datadog.Trace.OpenTracing
Provides OpenTracing support for Datadog APM |
|
Datadog.Monitoring.Distribution
Auto-instrumentation assets for Datadog APM |
|
Lucca.Logs.Shared
Lucca.Logs |
|
Datadog.Trace.BenchmarkDotNet
BenchmarkDotNet exporter for Datadog CI Visibility |
GitHub repositories (1)
Showing the top 1 popular GitHub repositories that depend on Datadog.Trace:
Repository | Stars |
---|---|
DataDog/dd-trace-dotnet
.NET Client Library for Datadog APM
|
Version | Downloads | Last updated | |
---|---|---|---|
3.7.0 | 8,670 | 12/18/2024 | |
3.6.1 | 83,149 | 11/26/2024 | |
3.6.0 | 75,963 | 11/19/2024 | |
3.5.0 | 135,890 | 11/6/2024 | |
3.4.1 | 105,124 | 10/28/2024 | |
3.4.0 | 29,836 | 10/24/2024 | |
3.3.1 | 386,085 | 9/18/2024 | |
3.3.0 | 30,281 | 9/16/2024 | |
3.2.0 | 161,526 | 9/2/2024 | |
3.1.0-prerelease | 1,286 | 8/14/2024 | |
3.0.0-prerelease | 769 | 7/29/2024 | |
2.61.0 | 26,370 | 11/6/2024 | |
2.60.0 | 52,347 | 10/24/2024 | |
2.59.0 | 130,570 | 9/16/2024 | |
2.58.0 | 63,496 | 9/2/2024 | |
2.57.0 | 353,724 | 8/14/2024 | |
2.56.0 | 253,552 | 7/25/2024 | |
2.55.0 | 91,063 | 7/18/2024 | |
2.54.0 | 171,785 | 7/9/2024 | |
2.53.2 | 1,674,934 | 6/19/2024 | |
2.53.1 | 93,602 | 6/17/2024 | |
2.53.0 | 173,857 | 6/11/2024 | |
2.52.0 | 612,872 | 5/23/2024 | |
2.51.0 | 515,398 | 5/6/2024 | |
2.50.0 | 404,228 | 4/17/2024 | |
2.49.0 | 776,800 | 3/18/2024 | |
2.48.0 | 1,067,731 | 2/29/2024 | |
2.47.0 | 708,553 | 2/14/2024 | |
2.46.0 | 682,531 | 1/24/2024 | |
2.45.0 | 313,092 | 1/10/2024 | |
2.44.0 | 532,463 | 12/19/2023 | |
2.43.0 | 396,065 | 12/5/2023 | |
2.42.0 | 259,221 | 11/21/2023 | |
2.41.0 | 909,767 | 11/6/2023 | |
2.40.0 | 521,258 | 10/16/2023 | |
2.39.0 | 89,773 | 10/11/2023 | |
2.38.0 | 393,225 | 9/20/2023 | |
2.37.0 | 628,624 | 8/31/2023 | |
2.36.0 | 368,590 | 8/23/2023 | |
2.35.0 | 376,363 | 7/31/2023 | |
2.34.0 | 39,176 | 7/25/2023 | |
2.33.0 | 304,392 | 7/4/2023 | |
2.32.0 | 346,825 | 6/20/2023 | |
2.31.0 | 597,118 | 5/31/2023 | |
2.30.0 | 757,883 | 5/5/2023 | |
2.29.0 | 374,441 | 4/17/2023 | |
2.28.0 | 107,919 | 4/12/2023 | |
2.27.0 | 561,720 | 3/24/2023 | |
2.26.0 | 354,483 | 3/9/2023 | |
2.24.1 | 779,464 | 2/27/2023 | |
2.24.0 | 51,833 | 2/24/2023 | |
2.23.0 | 594,262 | 2/8/2023 | |
2.22.0 | 580,611 | 1/24/2023 | |
2.21.0 | 466,168 | 12/20/2022 | |
2.20.0 | 490,877 | 12/2/2022 | |
2.19.0 | 462,467 | 11/10/2022 | |
2.18.0 | 850,230 | 10/25/2022 | |
2.17.0 | 1,003,629 | 10/11/2022 | |
2.16.0 | 75,812 | 10/7/2022 | |
2.15.0 | 414,008 | 9/26/2022 | |
2.14.0 | 547,120 | 8/23/2022 | |
2.13.0 | 282,560 | 8/3/2022 | |
2.12.0 | 431,603 | 7/13/2022 | |
2.11.0 | 524,057 | 6/22/2022 | |
2.10.0 | 363,770 | 6/9/2022 | |
2.9.0 | 810,112 | 5/13/2022 | |
2.8.0 | 351,129 | 5/5/2022 | |
2.7.0 | 330,838 | 4/22/2022 | |
2.6.0 | 574,938 | 4/7/2022 | |
2.5.1 | 269,118 | 3/25/2022 | |
2.4.4 | 896,839 | 3/16/2022 | |
2.4.3 | 480,319 | 3/2/2022 | |
2.4.2 | 107,934 | 2/25/2022 | |
2.4.1 | 5,204 | 2/24/2022 | |
2.4.0 | 17,266 | 2/22/2022 | |
2.3.0 | 465,185 | 2/10/2022 | |
2.2.0 | 204,869 | 2/2/2022 | |
2.1.1 | 384,575 | 1/19/2022 | |
2.1.0 | 505,999 | 1/7/2022 | |
2.0.1 | 448,240 | 12/20/2021 | |
2.0.0-prerelease | 14,325 | 12/10/2021 | |
1.31.2 | 407,234 | 2/22/2022 | |
1.31.1 | 39,256 | 12/21/2021 | |
1.31.0 | 308,967 | 12/2/2021 | |
1.30.1 | 131,919 | 11/24/2021 | |
1.30.0 | 432,977 | 11/16/2021 | |
1.29.1-prerelease | 66,241 | 10/28/2021 | |
1.29.0 | 958,008 | 10/15/2021 | |
1.28.8 | 114,787 | 9/29/2021 | |
1.28.7 | 170,799 | 9/14/2021 | |
1.28.6 | 71,144 | 9/8/2021 | |
1.28.5-prerelease | 862 | 8/30/2021 | |
1.28.4 | 178,194 | 8/30/2021 | |
1.28.3-prerelease | 435 | 8/17/2021 | |
1.28.2 | 229,407 | 8/4/2021 | |
1.28.1-prerelease | 543 | 7/14/2021 | |
1.28.0 | 246,278 | 7/12/2021 | |
1.27.1 | 815,029 | 6/16/2021 | |
1.27.0 | 178,708 | 6/2/2021 | |
1.26.3 | 442,647 | 5/11/2021 | |
1.25.2-prerelease | 2,556 | 4/2/2021 | |
1.25.0 | 442,173 | 3/22/2021 | |
1.24.0 | 366,234 | 2/23/2021 | |
1.23.0 | 296,717 | 2/3/2021 | |
1.22.2-prerelease | 449 | 2/1/2021 | |
1.22.1-prerelease | 469 | 1/28/2021 | |
1.22.0 | 213,200 | 1/14/2021 | |
1.21.2-prerelease | 3,054 | 12/21/2020 | |
1.21.1 | 69,123 | 12/17/2020 | |
1.21.0 | 115,478 | 11/25/2020 | |
1.20.0 | 331,980 | 11/3/2020 | |
1.19.6-prerelease | 1,568 | 10/15/2020 | |
1.19.5 | 376,572 | 10/7/2020 | |
1.19.4 | 106,357 | 9/29/2020 | |
1.19.3 | 180,735 | 9/17/2020 | |
1.19.2 | 274,653 | 8/31/2020 | |
1.19.1 | 703,940 | 8/10/2020 | |
1.19.0 | 69,699 | 8/7/2020 | |
1.18.3 | 205,795 | 7/17/2020 | |
1.18.2 | 56,121 | 7/9/2020 | |
1.18.1-prerelease | 578 | 7/6/2020 | |
1.18.0 | 35,350 | 6/25/2020 | |
1.17.1-prerelease | 630 | 6/23/2020 | |
1.17.0 | 422,435 | 5/15/2020 | |
1.16.3-prerelease | 592 | 5/13/2020 | |
1.16.2 | 56,098 | 5/5/2020 | |
1.16.1 | 235,231 | 4/20/2020 | |
1.16.0 | 42,049 | 4/2/2020 | |
1.15.1-prerelease | 702 | 3/30/2020 | |
1.15.0 | 260,422 | 3/23/2020 | |
1.14.2 | 19,134 | 3/13/2020 | |
1.14.1-prerelease | 530 | 3/12/2020 | |
1.14.0 | 7,678 | 3/9/2020 | |
1.13.4-prerelease | 1,530 | 3/4/2020 | |
1.13.3-prerelease | 602 | 2/24/2020 | |
1.13.2 | 118,315 | 2/21/2020 | |
1.13.0 | 364,407 | 2/14/2020 | |
1.12.0 | 101,932 | 2/5/2020 | |
1.11.1-prerelease | 1,412 | 1/13/2020 | |
1.11.0 | 129,485 | 12/11/2019 | |
1.10.3-prerelease | 673 | 12/11/2019 | |
1.10.2-prerelease | 584 | 12/10/2019 | |
1.10.1-prerelease | 720 | 12/10/2019 | |
1.10.0 | 77,125 | 11/27/2019 | |
1.9.1-prerelease | 1,065 | 11/14/2019 | |
1.9.0 | 204,177 | 11/7/2019 | |
1.8.0 | 204,610 | 10/17/2019 | |
1.7.0 | 95,404 | 9/10/2019 | |
1.6.2 | 84,629 | 8/20/2019 | |
1.6.1 | 21,857 | 8/14/2019 | |
1.6.0 | 81,725 | 7/20/2019 | |
1.4.1 | 358,394 | 6/26/2019 | |
1.4.0 | 68,086 | 6/20/2019 | |
1.2.0 | 70,949 | 5/20/2019 | |
1.1.0 | 87,578 | 4/17/2019 | |
1.0.0 | 80,377 | 4/5/2019 | |
0.8.2-beta | 9,537 | 3/28/2019 | |
0.8.1-beta | 2,311 | 3/21/2019 | |
0.8.0-beta | 1,984 | 3/11/2019 | |
0.7.1-beta | 51,532 | 1/31/2019 | |
0.7.0-beta | 29,929 | 1/17/2019 | |
0.6.0-beta | 74,838 | 12/21/2018 | |
0.5.2-beta | 29,426 | 12/4/2018 | |
0.5.1-beta | 11,412 | 11/20/2018 | |
0.5.0-beta | 612,636 | 10/30/2018 | |
0.4.1-beta | 2,898 | 10/23/2018 | |
0.4.0-beta | 1,010 | 10/12/2018 | |
0.3.2-beta | 2,061 | 9/26/2018 | |
0.3.1-beta | 1,116 | 9/21/2018 | |
0.3.0-beta | 951 | 9/13/2018 | |
0.2.4-alpha | 940 | 9/13/2018 |
See release notes at https://github.com/DataDog/dd-trace-dotnet/releases.
Please note that Datadog does not support tracing (manual or automatic) in partial-trust environments.