open-telemetry / open-telemetry/opentelemetry-python-contrib
AWS Lambda functions don't inject trace headers in responses
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 1.1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 16
Description
What problem do you want to solve?
When using auto-instrumentation for AWS Lambda functions, trace headers are not included in the HTTP response when integrated with API Gateway V2 (HTTP APIs).
Describe the solution you'd like
The auto-instrumentation layer should automatically inject trace headers into Lambda response objects when the function is invoked.
Describe alternatives you've considered
Manual header injection
Additional Context
No response
Would you like to implement a fix?
Yes
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.
Research direction
Start by locating the AWS Lambda auto-instrumentation and its handling of API Gateway V2 HTTP responses. Trace how Lambda response objects are produced, then verify that the completed response includes trace headers for HTTP API invocations. Done means covered behavior for automatic header injection, with tests demonstrating the response headers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- api, cloud, observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100