open-telemetry / open-telemetry/opentelemetry-python-contrib
AwsXRayPropagator Parent value in X-Amzn-Trace-Id header generator
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 1.1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 16
Description
Env :
- Python app
- EKS cluster
- AWS ALB
- istio service mesh
- otel autoinstrumentation.
Is your feature request related to a problem?
XRay propagator expects a traceid header. However, when parent field is not set, trace is seen as invalid. Problem was described in the following issue
When using an AWS applicative load balancer, header is present but without Parent set.
Describe the solution you'd like
Propagator should consider trace as root and generate an id if none is provided.
Describe alternatives you've considered
We can use the propagator by rewriting headers in istio and adding a static parent header before they go in the app.
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.
Research direction
Start by locating the Python AwsXRayPropagator entry point and review the related behavior described in issue 1378. Confirm how headers without a Parent value are handled. Done means such headers are treated as root traces with a generated id and the existing propagator behavior remains valid for headers that include Parent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100