open-telemetry / open-telemetry/opentelemetry-java-contrib
OTEL xray propagator cannot process xray header without parent segment
@wangzlei is already working on this.
Since Oct 31, 2025.
- Dominant language
- Java
- Stars
- 269
- Forks
- 196
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 38
Description
Component(s)
aws-xray-propagator
What happened?
The aws-xray-propagator does not work, if it receives a x-amzn-trace-id without the optional parent segment.
Description
The AWS ALB adds the amazon x-amzn-trace-id header to each request.
Details see https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-request-tracing.html
The xray traceId looks like this:
X-Amzn-Trace-Id: Root=1-67891233-abcdef012345678912345678
Note that the traceId does not contain the parent segment.
The parent segment is optional according to xray format spec.
Due to the missing parent segment, the traceId is not accepted and a new traceId is generated.
Expected Result
The aws-xray-propagator shall extract the traceId from the x-amzn-trace-id header.
Actual Result
The aws-xray-propagator is creating a new traceId, because of the missing parent segment
Component version
1.51.0-alpha
Log output
No response
Additional context
No response
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.
Contributor 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.
Assessment
This issue has not been assessed yet.