[BUG]: Provide a consistent way to disable datadog in CI and Locally

[jarshwah]

Tracer Version(s)

3.13.0

Python Version(s)

Python 3.13.2

Pip Version(s)

dont.use.pip

Bug Report

It's extremely difficult to fully disable datadog logging and connection attempts locally and when running in CI. A recent change meant that our local development logs were being flooded with datadog logs and trace connection errors.

Here is the current set of environment variables we configure to try and silence as much as we can:

export DD_DOGSTATSD_DISABLE=1
export DD_APM_TRACING_ENABLED=false
export DD_IAST_ENABLED="false"
export DD_INSTRUMENTATION_TELEMETRY_ENABLED=false
export DD_PROFILING_ENABLED="false"
export DD_RUNTIME_METRICS_ENABLED="false"
export DD_TRACE_ENABLED=false
export DD_TRACE_OTEL_ENABLED="false"

In particular, DD_APM_TRACING_ENABLED seems to have been added recently, or has updated what it was scoped to block.

Note the combination of _ENABLED and _DISABLE suffixes and the various values of 1/false/"false" that seemingly have no consistency.

It's incredibly frustrating trying to divine the exact keys and values required to turn off datadog. Ideally, there'd be a top level DD_ENABLED=0 that would override the full suite of options. Without that, having a clearly documented list of keys and their values would be the next best thing.

Reproduction Code

No response

Error Logs

No response

Libraries in Use

No response

Operating System

No response

[marcelofern]

+1 on this. After changing a few settings on my local environment I am back to playing with different combinations of 0 and "false" and false to silence datadog.