Report OTLP export status in tracer startup log

[bm1549]

What Does This Do

Adds three boolean fields to the "DATADOG TRACER CONFIGURATION" startup log emitted by dd-trace-core's StatusLogger.toJson:

• otlp_traces_export_enabled: config.isTraceOtlpExporterEnabled()
• otlp_metrics_export_enabled: config.isMetricsOtelEnabled() && config.isMetricsOtlpExporterEnabled()
• otlp_logs_export_enabled: config.isLogsOtelEnabled() && config.isLogsOtlpExporterEnabled()

Also adds a new StatusLoggerTest covering the default (disabled) case, the fully-enabled case, and the case where the OTLP exporter is selected but the metrics and logs OTel signals stay disabled.

Motivation

Part of a cross-tracer effort to report OTLP export status in each tracer's startup log. The JSON keys are identical across the dd-trace-* libraries so the fields can be read the same way regardless of language.

Additional Notes

Traces report directly from the OTLP exporter setting. Metrics and logs require both the OTel signal to be enabled and the OTLP exporter to be selected, so those two fields combine both checks.

This is a diagnostic logging change and does not alter tracer runtime behavior.

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Once approved, use merge queue to merge the PR

---

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 dd-trace-py#19265
• dd-trace-java: Report OTLP export status in tracer startup log #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 dd-trace-py#19266

[datadog-official]

🎯 Code Coverage (details)
• Patch Coverage: 0.00%
• Overall Coverage: 57.55% (-0.03%)

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

[dd-octo-sts]

🟡 Java Benchmark SLOs — Performance SLO warning (near threshold)

Suite	Status
Startup	🟡 warning

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	13.99 s	13.93 s	[-0.3%; +1.1%] (no difference)
startup:insecure-bank:tracing:Agent	12.94 s	13.06 s	[-1.5%; -0.4%] (maybe better)
startup:petclinic:appsec:Agent	16.92 s	16.89 s	[-0.5%; +0.9%] (no difference)
startup:petclinic:iast:Agent	16.27 s	16.94 s	[-8.1%; +0.1%] (no difference)
startup:petclinic:profiling:Agent	16.54 s	16.88 s	[-3.2%; -0.8%] (maybe better)
startup:petclinic:sca:Agent	16.95 s	16.75 s	[+0.2%; +2.2%] (maybe worse)
startup:petclinic:tracing:Agent	16.14 s	16.10 s	[-0.8%; +1.3%] (no difference)

Commit: a4287c54 · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.