Skip to content
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

Changing DSN breaks current AWS Lambda integration #5211

Closed
3 tasks done
antonpirker opened this issue Jun 7, 2022 · 0 comments · Fixed by #5212
Closed
3 tasks done

Changing DSN breaks current AWS Lambda integration #5211

antonpirker opened this issue Jun 7, 2022 · 0 comments · Fixed by #5212
Assignees

Comments

@antonpirker
Copy link
Member

Is there an existing issue for this?

How do you use Sentry?

Sentry Saas (sentry.io)

Which package are you using?

@sentry/serverless

SDK Version

V7

Framework Version

No response

Link to Sentry event

No response

Steps to Reproduce

See description here: #5126

Expected Result

The AWS Lambda integration should work in V7 out of the box. Right now it sends errors to localhost:3000 and not sentry.io

Actual Result

Send Sentry data directly to sentry.io (not localhost:3000)

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

Successfully merging a pull request may close this issue.

2 participants