feat: report OTLP export status in startup log

[bm1549]

Description

Adds three boolean fields to the tracer's startup diagnostic log ("DATADOG TRACER CONFIGURATION"), emitted from collect() in ddtrace/internal/debug.py:

• otlp_traces_export_enabled: reflects agent_config.trace_otlp_export_enabled (OTLP trace export, opt-in via OTEL_TRACES_EXPORTER=otlp)
• otlp_metrics_export_enabled: reflects config._otel_metrics_enabled
• otlp_logs_export_enabled: reflects config._otel_logs_enabled

This makes the OTLP export configuration visible in the startup log, which helps with support and debugging. It is part of a cross-tracer effort, so the JSON keys are identical across the dd-trace-* libraries.

Testing

• test_standard_tags asserts the three keys are present and boolean.
• test_otlp_export_enabled_fields_default runs in a subprocess with the OTLP-related env cleared and asserts all three default to False.
• test_otlp_export_enabled_fields_set runs in a subprocess with OTEL_TRACES_EXPORTER=otlp and the metrics/logs flags enabled, and asserts all three report True.

Risks

None. The change only adds fields to an existing diagnostic log. No existing fields or behavior change.

Additional Notes

No release note is needed: this change only adds fields to the tracer's internal startup diagnostic log and does not change customer-facing behavior. The PR carries the changelog/no-changelog label.

---

Related PRs — cross-tracer OTLP startup-log effort

• dd-trace-js: feat(startup-log): report OTLP export status dd-trace-js#9517
• dd-trace-py: feat: report OTLP export status in startup log #19265
• dd-trace-java: Report OTLP export status in tracer startup log dd-trace-java#12062
• dd-trace-dotnet: Report OTLP export status in tracer startup log dd-trace-dotnet#8936
• dd-trace-rb: Report OTLP export status in startup log dd-trace-rb#6096
• dd-trace-go: feat(tracer): report OTLP export status in startup log dd-trace-go#5062
• dd-trace-php: feat(tracing): report OTLP export status in startup log dd-trace-php#4056
• system-tests: Cover OTLP export status in startup logs [dotnet@brian.marks/otlp-export-startup-log][nodejs@brian.marks/otlp-export-startup-log][python@brian.marks/otlp-export-startup-log][ruby@brian.marks/otlp-export-startup-log] system-tests#7376
• Related dd-trace-py fix (OTLP logs self-export loop, surfaced by this work): fix(opentelemetry): prevent OTLP logs self-export loop #19266

[datadog-datadog-prod-us1-2]

 

✨ Unblock PR with BitsAI

⚠️ Warnings

🚦 10 Pipeline jobs failed

DataDog/apm-reliability/dd-trace-py | build linux serverless: [amd64, cp315-cp315, v113741238-d2b8243-manylinux2014_x86_64, 1]     

DataDog/apm-reliability/dd-trace-py | build linux serverless: [amd64, cp315-cp315, v113741491-d2b8243-musllinux_1_2_x86_64, 1]     

DataDog/apm-reliability/dd-trace-py | build linux serverless: [arm64, cp315-cp315, v113741357-d2b8243-manylinux2014_aarch64, 1]     

View all 10 failed jobs.

ℹ️ Info

No other issues found (see more)

🧪 All tests passed
❄️ No new flaky tests detected

🔄 Datadog auto-retried 1 job - 1 passed on retry

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 0025fca | Docs | Datadog PR Page | Give us feedback!}

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-07-24 21:58:29

Comparing candidate commit 0025fca in PR branch brian.marks/otlp-export-startup-log with baseline commit e083509 in branch main.

Found 0 performance improvements and 5 performance regressions! Performance is the same for 612 metrics, 10 unstable metrics.

scenario:iastaspects-lstrip_aspect

• 🟥 execution_time [+52.545µs; +59.053µs] or [+16.275%; +18.290%]

scenario:iastaspects-translate_aspect

• 🟥 execution_time [+43.695µs; +51.719µs] or [+8.727%; +10.330%]

scenario:iastaspectsospath-ospathbasename_aspect

• 🟥 execution_time [+85.648µs; +93.001µs] or [+20.155%; +21.886%]

scenario:span-start

• 🟥 execution_time [+1.353ms; +1.511ms] or [+8.636%; +9.641%]

scenario:telemetryaddmetric-1-count-metric-1-times

• 🟥 execution_time [+210.895ns; +248.018ns] or [+9.944%; +11.695%]

[cit-pr-commenter-54b7da]

Codeowners resolved as

ddtrace/internal/debug.py                                               @DataDog/apm-core-python
tests/integration/test_debug.py                                         @DataDog/apm-core-python

[cit-pr-commenter-54b7da]

Circular import analysis

🚨 New circular imports detected 🚨

15 new circular import(s) have been introduced by this PR:

Show new cycles (showing 5 of 15 shortest)

ddtrace.internal.datastreams -> ddtrace.internal.datastreams.botocore -> ddtrace.internal.datastreams
ddtrace.internal.datastreams -> ddtrace.internal.datastreams.kombu -> ddtrace.internal.datastreams
ddtrace.internal.datastreams -> ddtrace.internal.datastreams.google_cloud_pubsub -> ddtrace.internal.datastreams
ddtrace.internal.datastreams -> ddtrace.internal.datastreams.kafka -> ddtrace.internal.datastreams
ddtrace.internal.datastreams -> ddtrace.internal.datastreams.aiokafka -> ddtrace.internal.datastreams

To see all cycles, download the cycles-base.json and cycles-pr.json artifacts from this CI job and run:

uv run --script scripts/import-analysis/cycles.py compare cycles-base.json cycles-pr.json

Please consider refactoring your changes in accordance to the Separation of Concerns principle.

⚠️ Existing circular imports

There are 18 circular imports that already exist on the base branch and have not been changed by this PR.

Show existing cycles (showing 5 of 18 shortest)

ddtrace._trace.span -> ddtrace.internal.core -> ddtrace._trace.span
ddtrace.trace -> ddtrace._trace.tracer -> ddtrace.internal.debug -> ddtrace.trace
ddtrace -> ddtrace.trace -> ddtrace._trace.tracer -> ddtrace.internal.debug -> ddtrace
ddtrace -> ddtrace.trace -> ddtrace._trace.tracer -> ddtrace.internal.debug -> ddtrace.internal.runtime.runtime_metrics -> ddtrace
ddtrace._trace.span -> ddtrace._trace.context -> ddtrace.internal.utils.http -> ddtrace.internal.utils -> ddtrace.internal.core -> ddtrace._trace.span

To see all cycles, download the cycles-base.json and cycles-pr.json artifacts from this CI job and run:

uv run --script scripts/import-analysis/cycles.py compare cycles-base.json cycles-pr.json