ref(serverless): Point DSN to relay in lambda extension

[antonpirker]

If the serverless SDK is running in an AWS Lambda Function it should not send data directly to sentry.io but to the relay that is running in the AWS Lambda Extension (which is running on localhost:3000)

This PR parses the DSN and changes the host and port to point to localhost:3000.

[github-actions]

size-limit report 📦

Path	Size
@sentry/browser - ES5 CDN Bundle (gzipped + minified)	18.75 KB (-6.91% 🔽)
@sentry/browser - ES5 CDN Bundle (minified)	58.19 KB (-9.95% 🔽)
@sentry/browser - ES6 CDN Bundle (gzipped + minified)	17.65 KB (-6.45% 🔽)
@sentry/browser - ES6 CDN Bundle (minified)	52.09 KB (-10.14% 🔽)
@sentry/browser - Webpack (gzipped + minified)	19.33 KB (-16.82% 🔽)
@sentry/browser - Webpack (minified)	61.44 KB (-24.81% 🔽)
@sentry/react - Webpack (gzipped + minified)	19.35 KB (-16.87% 🔽)
@sentry/nextjs Client - Webpack (gzipped + minified)	42.82 KB (-10.91% 🔽)
@sentry/browser + @sentry/tracing - ES5 CDN Bundle (gzipped + minified)	24.41 KB (-6.4% 🔽)
@sentry/browser + @sentry/tracing - ES6 CDN Bundle (gzipped + minified)	23 KB (-6.08% 🔽)

[AbhiPrasad]

Isn't this a breaking change? What if someone does not want to use the AWS Lambda Extension?

[jshearer]

Hi there @AbhiPrasad @sl0thentr0py @antonpirker! We just tried to set up Sentry in AWS lambda, and through much debugging and digging, came across this commit/PR. Uh.. are there any docs on this? What is AWS lambda extension? How do we report data from lambda to sentry? As it is right now, we just get opaque "connection refused to 127.0.0.1:3000" errors... ☹️

Edit: We followed the docs here, which mention nothing about this stuff :s

Edit 2: For any folks coming to find this from search, we solved this by pinning our sentry dependencies to 6.x, as clearly 7.x is not supposed to be live yet

Thanks!

[antonpirker]

Hey @jshearer
Thanks for reporting this and sorry for your inconveniences!
This is entirely my fault. This PR should not have been released with V7, because it belongs to the new AWS Lambda integration we are developing right now.

I will supply a patch as soon as possible.
In the mean time, yes pinning to 6.x is the best way to "fix" this. But soon we will release an update to 7.x to include a patch for this, so you get also all the new 7.x stuff!

I will keep you posted!

[antonpirker]

Hey @jshearer !

Just for the record, you did everything correct! I messed up.
I created a patch for this in #5212 and this will be released soon.