Hang on, I already use Sentry
Keep @sentry/aws-serverless and change its destination to your Telebugs DSN. Your error reports stay on your server. You don’t need a Sentry account.
A Lambda invocation is brief. The error report should stick around. The Sentry AWS SDK sends it to Telebugs on your server.
Space pauses or resumes. R replays. Escape shows the complete setup.
Keep @sentry/aws-serverless and change its destination to your Telebugs DSN. Your error reports stay on your server. You don’t need a Sentry account.
The Lambda wrapper handles sending captured errors before the invocation finishes. Your Telebugs server keeps the report after the function has stopped.
No. The SDK sends reports to your Telebugs DSN. Your function needs network access to that endpoint, not an AWS account integration inside Telebugs.