Baggage injected via DD_TRACE_HEADER_BAGGAGE is not retrievable via OTEL Baggage API

Open

#10,031 opened on Nov 25, 2025 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 35/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Stale
Tech stack: java
Domain: observability-sre

Research direction

Start by reproducing the issue with DD_TRACE_HEADER_BAGGAGE and DD_TRACE_OTEL_ENABLED, then inspect the path from the incoming headers to Baggage.current().asMap(). Done means the OTEL Baggage API exposes the same mapped properties as the Datadog internal tracer baggage for the supplied request.

Written by the indexing model from the issue text.

Description

comp: context propagation type: bug report

Tracer Version(s)

1.56.1~b8849a9451

Java Version(s)

21.0.9

JVM Vendor

Eclipse Adoptium / Temurin

Bug Report

Baggage mapped into the trace baggage via DD_TRACE_HEADER_BAGGAGE is not retrievable via OTEL Context.

Expected Behavior

I expect OTEL Baggage to be the same as Datadog Internal Tracer Baggage

Reproduction Code

ENV:

DD_ENV=dev
DD_INTEGRATIONS_ENABLED=true
DD_REMOTE_CONFIGURATION_ENABLED=false
DD_SERVICE=example
DD_SERVICE_NAME=example
DD_TELEMETRY_DEPENDENCY_COLLECTION_ENABLED=false
DD_TRACE_DEBUG=true
DD_TRACE_HEADER_BAGGAGE=comp-business-process-id:company.businessProcessId,comp-business-process-name:company.businessProcessName
DD_TRACE_OTEL_ENABLED=true

HTTP Call with headers:

GET http://localhost:8504/client
comp-business-process-id: this-is-a-bpid-keep-it
comp-business-process-name: this-is-a-bpid-name-keep-it

Retrieving baggas as map should contain the mentioned properties.

Baggage.current().asMap()

Dominant language: Java
Stars: 737
Forks: 361
Avg merge: 3d 20h
Merged PRs (30d): 173

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

Compatibility certification request for FJ-EAP 2.1.0 for Jakarta EE Platform 11 Open

certification

Difficulty 1/5 Under an hour Newbie friendliness 80/100

jakartaee/platform#1359 · Opened Sep 24, 2026
Python guide test runner copies stale Micronaut Test Resources state Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

micronaut-projects/micronaut-guides#1856 · Opened Sep 23, 2026
[BUG] ECR GetAuthorizationToken returns a proxyEndpoint for the default region, not the request's Open

bug ecr

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

floci-io/floci#4264 · Opened Sep 23, 2026
Drop point numbers from GitHub milestones Open

Needs: Triage Type: Feature request

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

AntennaPod/AntennaPod#8794 · Opened Sep 23, 2026
[aw] Issue Classification Agent timed out Open

agentic-workflows

Difficulty 2/5 1-3 hours Newbie friendliness 65/100

github/copilot-sdk#2760 · Opened Sep 23, 2026

More Java issues