Ensure all exceptions and messages have been sent to Sentry before returning
arabold opened this issue · 3 comments
arabold commented
See getsentry/raven-node#338 for more details
Without this we risk to miss errors and messages as they are never sent out.
bericp1 commented
Hey @arabold -- have you seen getsentry/sentry-javascript#1380
The new unified SDK seems to have remedied this. Not sure if it's crossed your radar or planned for development or not.
The new node SDK is @sentry/node
and they explicitly address draining here in the docs.
I realize this means rewriting arabold/serverless-sentry-lib to use @sentry/node
but figured I'd drop some links here for the sake of drawing your attention to it.
arabold commented
Thanks. Indeed I missed that update.
demetrio812 commented
Hello, is this the reason why I don't get any messages logged (using AWS Lambda)? Is there a workaround? Thanks