Skip to content

Conversation

msonnb
Copy link

@msonnb msonnb commented Aug 4, 2025

Which problem is this PR solving?

Fixes #2827

Short description of the changes

Adds support for AWS Lambda streaming handlers by checking if the handler has the special aws.lambda.runtime.handler.streaming symbol.

@msonnb msonnb requested a review from a team as a code owner August 4, 2025 09:18
Copy link

linux-foundation-easycla bot commented Aug 4, 2025

CLA Signed

The committers listed above are authorized under a signed CLA.

  • ✅ login: msonnb / name: Martin Sonnberger (74ab471)

@github-actions github-actions bot requested a review from jj22ee August 4, 2025 09:18
@msonnb msonnb changed the title feat(instrumentation-aws-lamda): support streaming handlers feat(instrumentation-aws-lambda): support streaming handlers Aug 4, 2025
this._endSpan(span, undefined, () => resolve(value))
);
},
(err: Error | string) => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it intentional that the promise fails silently in this scenario?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not fully sure what you mean 🤔 we return a new promise that rejects with the error after the span is ended, so it shouldn't fail silently? (Also I didn't change this part, just extracted it into a function)

@pichlermarc
Copy link
Member

cc @jj22ee (component owner)

@jj22ee
Copy link
Contributor

jj22ee commented Aug 28, 2025

Hey, thanks for the fix. Planning to take a look this week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

AWS Lambda Instrumentation causes lambda failures when using streaming response
4 participants