dd-trace-dotnet
dd-trace-dotnet copied to clipboard
DataDog
.NET Client Library for Datadog APM
**Describe the bug** It throws an error after using latest version of Nuget package in our .Net core Application. we are using .Net Core 3 WebAPI Angular 8 **To Reproduce**...
**Describe the bug** The [documentation](https://docs.datadoghq.com/tracing/setup_overview/setup/dotnet-core/?tab=code#enable-the-tracer-for-your-service) suggests that configuration set in code should take precedence, but this doesn't seem to be true in practice. When setting configuration in code I can...
**Describe the bug** I'm evaluating Datadog with a network of .NET Core services running in Linux containers. In each of the containers, I've set DD_SERVICE environment variable to the name...
The new serverless docker files were adding benign errors to the build logs, and were doing additional downloads of the tracer home directory. This tidies up the build slightly, without...
Fixes #1571 Changes proposed in this pull request: Add Support for DD_TRACE_DB_CLIENT_SPLIT_BY_INSTANCE @DataDog/apm-dotnet
running with a docker container built with package datadog-dotnet-apm_1.28.8_amd64.deb we need to have HTTP_PROXY env settings for the main application, but I also need to disable it for the DD_tracer...
This adds several CallTarget instrumentation points to invoke the same logic as our AspNetCore integration that's built-in for our netstandard2.0/netcoreapp build targets. However, since we can't refer to the abstraction...
Resolves the security alert for MessagePack 1.9.3, see https://github.com/advisories/GHSA-7q36-4xx7-xcxf I recommend looking commit by commit, or at least skipping 4f538eda42325b98dab8d88871d52184ca29a582 which is where I ran the `nuke update-vendored-code` tool. TODO:...
I have my own way of triggering a downstream call to another process that I want to correlate with the upstream process trace. I don't see a way with the...
**Describe the bug** Memory leak due to `[ThreadStatic]` when no synchronization context is present. **To Reproduce** Steps to reproduce the behavior: 1. Enable tracer for any long running ASP.NET Core...
