-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create @sentry/profiling-node
Lambda Layer
#13049
Comments
@sentry/profiling-node
Lambda Layer
Would really like to see this. Am having issues with esbuild not copying over .node files even with '.node': 'copy', and this would solve that. |
@FredrikZeiner I think this may be related to some recent changes in the package that broke this. It is probably related to this issue. Would you mind downgrading the version to |
That did indeed solve it! I've been going at this for a few hours even pulling in esbuild-plugin-copy. Thank you! Sign me up still for the layer though. Am already using SentryNodeServerlessSDK. |
Can confirm upgrading past 8.48.0 broke functionality on lambda, even with
in my esbuild config |
As highlighted here, there are a few steps needed to successfully make use of
@sentry/profiling-node
in serverless environments.While there are clear benefits to users bundling all of their code on those environments, it's a complicated process. People often use tools that abstract away low level interactions with bundlers, like AWS SAM, which makes it even harder to follow the outlined steps.
We can alleviate that by publishing an AWS Lambda layer for
@sentry/profiling-node
that people can add to their Lambda functions to use@sentry/profling-node
out of the box.Relevant issue: #12994
cc @JonasBa
The text was updated successfully, but these errors were encountered: