[BUG]: DD_TRACE_ENABLED set to false is still sending traces

[wr-cdargis]

Tracer Version(s)

arn:aws:lambda:us-east-1:464622532012:layer:dd-trace-dotnet:20

Operating system and platform

aws lambda

Instrumentation Mode

manual with cdk/cloud formation

TFM

net8.0

Bug Report

For DD_TRACE_ENABLED : the documentation says:

"Enables or disables all instrumentation."

We have:

1. the dotnet tracing layer installed

2. the env variables configured to DISABLE the extension/layer

3. evidence in Datadog UI that the extension is still sending tracing.

The obvious concern here is cost.

See the layers installed:

With the env variable DD_TRACE_ENABLED set to false:

DatadogUI still shows traces being sent:

Reproduction Code

No response

[lucaspimentel]

Hey @wr-cdargis. Thanks for reporting this issue. This was already reported in the repository for the AWS Lambda layer for .NET (DataDog/dd-trace-dotnet-aws-lambda-layer#14) and we started working on a fix (#6781).

In the mean time, you can set CORECLR_ENABLE_PROFILING=false instead. This is a .NET runtime configuration which disables the Profiling APIs used by the .NET tracing library, so dd-trace-dotnet is not even loaded at all into your Lambda function.

[wr-cdargis]

@lucaspimentel ah ok that explains why I could not find an issue in this repo. I was surprised to be the first to stumble onto this. Thank you for the quick response.

[wr-cdargis]

@lucaspimentel CORECLR_ENABLE_PROFILING=false does not seem to be working.