Skip to content

Changing DSN breaks current AWS Lambda integration #5211

Closed
@antonpirker

Description

@antonpirker

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)

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions