The .NET Tracer supports all .NET-based languages (for example, C#, F#, Visual Basic).
The .NET Tracer supports instrumentation on:
The .NET Tracer library for Datadog is open-source. For more information see the tracer Github repository.
The .NET Tracer can instrument the following libraries automatically:
Framework or library | NuGet package | Integration Name |
---|---|---|
ASP.NET Core | Microsoft.AspNetCore Microsoft.AspNetCore.App 2.0+ and 3.0+ | AspNetCore |
ADO.NET | System.Data.Common System.Data.SqlClient 4.0+ | AdoNet |
HttpClient / HttpMessageHandler | System.Net.Http 4.0+ | HttpMessageHandler |
WebClient / WebRequest | System.Net.Requests 4.0+ | WebRequest |
Redis (StackExchange client) | StackExchange.Redis 1.0.187+ | StackExchangeRedis |
Redis (ServiceStack client) | ServiceStack.Redis 4.0.48+ | ServiceStackRedis |
Elasticsearch | Elasticsearch.Net 5.3.0+ | ElasticsearchNet |
MongoDB | MongoDB.Driver.Core 2.1.0+ | MongoDb |
PostgreSQL | Npgsql 4.0+ | AdoNet |
RabbitMQ | RabbitMQ.Client 3.6.9+ | RabbitMQ |
DbCommand
abstract class or the IDbCommand
interface, regardless of the underlying implementation. It also instruments direct calls to SqlCommand
.Don’t see your desired frameworks? Datadog is continually adding additional support. Check with the Datadog team for help.
The .NET Tracer works on .NET Core 2.0, 2.2, and 3.0, but these versions reached their end of life and are no longer supported by Microsoft. See Microsoft’s support policy for more details. We recommend using the latest patch version of .NET Core 2.1 or 3.1. Older versions of .NET Core may encounter the following runtime issues when enabling automatic instrumentation:
Issue | Affected .NET Core Versions | Solution | More information |
---|---|---|---|
JIT Compiler bug on Linux/x64 | 2.0.x,2.1.0-2.1.11,2.2.0-2.2.5 | Upgrade .NET Core to the latest patch version, or follow steps in the linked issue | DataDog/dd-trace-dotnet/issues/302 |
Resource lookup bug with a non en-US locale | 2.0.0 | Upgrade .NET Core to 2.0.3 or above | dotnet/runtime/issues/23938 |
Documentation, liens et articles supplémentaires utiles: