AWS Lambda Traceparent Propagation

[aaaugustine29]

Hi All,
I want to ask if anyone has successfully had the traceparent be properly extracted by OTel when using an AWS Lambda, and receiving an http request from another service that is instrumented. I was able to gain this functionality, but it required some helper functions to manually extract the traceparent header (and other context) from the http request coming into the API gateway/lambda.

I wanted to check and see if there was anyone who has had success without having to do any sort of manual propagation prior to raising the alarm on this a little more. If nobody has had success, I will move forward with trying to get some sort of functionality added in a way similar to the way I have achieved it. The pieces that allowed for my success are outline below.

1. Create additional function that wraps lambda handler. For instance, the lambda handler singature "export const pictureServerHandler = async (event, context)" is exported with a wrapper function "export const lambdaHandler = extractTraceContext(pictureServerHandler);"
2. The extraction wrapper function essentially just manually inserts the context into opentelemetry.
3. To keep performance, the traceProvider and metricprovider are exported, and then are flushed in the wrapper function once the original handler finished execution

This was what was required for us to get full functionality while maintaining a reasonable level of performance. I want to hear whether this is necessary, and if not, what you all did to allow the traceparent to be properly propagated?

Feel free to ask any questions, sorry if what I'm describing is unclear but if this is something that isn't currently supported, I want to share my works!