feat: report OTLP export status in startup log#19265
Draft
bm1549 wants to merge 1 commit into
Draft
Conversation
Add three boolean fields to the tracer's startup diagnostic log
("DATADOG TRACER CONFIGURATION") indicating whether each telemetry
signal is exported over OTLP:
- otlp_traces_export_enabled: reflects agent_config.trace_otlp_export_enabled
(opt-in via OTEL_TRACES_EXPORTER=otlp; export is routed through
libdatadog's native OTLP trace exporter)
- otlp_metrics_export_enabled: reflects config._otel_metrics_enabled
- otlp_logs_export_enabled: reflects config._otel_logs_enabled
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
bm1549
added
the
AI Generated
This was referenced Jul 24, 2026
Contributor
🎉 All green!🧪 All tests passed 🔄 Datadog auto-retried 2 jobs - 2 passed on retry 🔗 Commit SHA: e09dd49 | Docs | Datadog PR Page | Give us feedback! |
BenchmarksBenchmark execution time: 2026-07-24 02:08:06 Comparing candidate commit e09dd49 in PR branch Found 0 performance improvements and 5 performance regressions! Performance is the same for 613 metrics, 10 unstable metrics. scenario:iastaspects-index_aspect
scenario:iastaspectsospath-ospathbasename_aspect
scenario:span-start
scenario:telemetryaddmetric-1-count-metric-1-times
scenario:tracer-small
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds three boolean fields to the tracer's startup diagnostic log ("DATADOG TRACER CONFIGURATION"), emitted from
collect()inddtrace/internal/debug.py:otlp_traces_export_enabled: reflectsagent_config.trace_otlp_export_enabled(OTLP trace export, opt-in viaOTEL_TRACES_EXPORTER=otlp)otlp_metrics_export_enabled: reflectsconfig._otel_metrics_enabledotlp_logs_export_enabled: reflectsconfig._otel_logs_enabledThis 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_tagsasserts the three keys are present and boolean.test_otlp_export_enabled_fields_defaultruns in a subprocess with the OTLP-related env cleared and asserts all three default toFalse.test_otlp_export_enabled_fields_setruns in a subprocess withOTEL_TRACES_EXPORTER=otlpand the metrics/logs flags enabled, and asserts all three reportTrue.Risks
None. The change only adds fields to an existing diagnostic log. No existing fields or behavior change.
Additional Notes
Includes a release note under
other.Related PRs — cross-tracer OTLP startup-log effort