Ensure OTLP Traces Endpoint uses OTLP Traces Protocol Config

[mhlidd]

What Does This Do

Previously, OTLP Traces Endpoint was fetched based on the protocol set by the OTLP Metrics Protocol config. This PR replaces that w/ the config set by the OTLP Traces Protocol instead.

Motivation

Additional Notes

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
  Use solves instead, and assign the PR milestone to the 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

Jira ticket: [PROJ-IDENT]

[dd-octo-sts]

Hi! 👋 Thanks for your pull request! 🎉

To help us review it, please make sure to:

• Add at least one type, and one component or instrumentation label to the pull request

If you need help, please check our contributing guidelines.

[datadog-official]

More details

The default OTLP traces endpoint now follows the OTLP traces protocol. This behavior agrees with the related OTLP endpoint selection logic.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Datadog Autotest · Commit 158a24f · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest}

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

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	14.72 s	14.58 s	[+0.2%; +1.6%] (maybe worse)
startup:insecure-bank:tracing:Agent	13.66 s	13.67 s	[-0.8%; +0.7%] (no difference)
startup:petclinic:appsec:Agent	16.61 s	16.77 s	[-5.4%; +3.5%] (no difference)
startup:petclinic:iast:Agent	17.00 s	17.00 s	[-0.8%; +0.9%] (no difference)
startup:petclinic:profiling:Agent	16.83 s	16.87 s	[-1.5%; +1.0%] (no difference)
startup:petclinic:sca:Agent	16.98 s	16.83 s	[-0.1%; +1.8%] (no difference)
startup:petclinic:tracing:Agent	15.66 s	16.29 s	[-7.9%; +0.2%] (no difference)

Commit: 158a24f2 · 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.

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-09-01 20:32:39 UTC ℹ️ Start processing command /merge

---

2026-09-01 20:32:44 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 1h (p90).

---

2026-09-01 21:22:12 UTC ❌ MergeQueue: The build pipeline contains failing jobs for this merge request

Build pipeline has failing jobs for 9c0cbfb:

• test_inst: [oracle8, 5/8]

⚠️ Do NOT retry failed jobs directly (why?).

What to do next?

• Investigate the failures and when ready, re-add your pull request to the queue!
• If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
• Any question, go check the FAQ.

Details

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected and the pipeline got canceled.

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-09-01 21:54:11 UTC ℹ️ Start processing command /merge

---

2026-09-01 21:54:17 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 1h (p90).

---

2026-09-01 22:39:41 UTC ℹ️ MergeQueue: This merge request was merged