Problem Statement
it would still be nice to have more options for configuring auto-instrumentation, either via environment variables or through an client configuration interface.
In particular, I'm looking for ways to filter out 4xx status codes in Sentry. This is currently possible with Sentry.init.
Additionally, the data scraping to comply with DVSGO should be either enabled by default or configurable at the global scope.
Q: What happens when using auto-instrumentation and then Sentry.init() inside the Lambda? Will this work without problems?
Solution Brainstorm
add an interface to configure an already created client
Additional Context
I have been trying to realize https://docs.sentry.io/platforms/javascript/guides/aws-lambda/install/layer/#option-b-manual-setup, but it completely fails for me when using CDK. The instrumentation file is not bundled with the Lambda.
Priority
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it.
Problem Statement
it would still be nice to have more options for configuring auto-instrumentation, either via environment variables or through an client configuration interface.
In particular, I'm looking for ways to filter out 4xx status codes in Sentry. This is currently possible with
Sentry.init.Additionally, the data scraping to comply with DVSGO should be either enabled by default or configurable at the global scope.
Q: What happens when using auto-instrumentation and then
Sentry.init()inside the Lambda? Will this work without problems?Solution Brainstorm
add an interface to configure an already created client
Additional Context
I have been trying to realize https://docs.sentry.io/platforms/javascript/guides/aws-lambda/install/layer/#option-b-manual-setup, but it completely fails for me when using CDK. The instrumentation file is not bundled with the Lambda.
Priority
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding
+1orme too, to help us triage it.