Before submitting a pull request, please take a look at our
Contributing guidelines and verify:

• If you've added code that should be tested, please add tests.
• Ensure your code lints and the test suite passes (yarn lint) & (yarn test).

Background

• My team runs Express inside Lambda - we have a monolithic Lambda function with express handling routing, middleware, etc
• We are using @sentry/node today, and tried adding @sentry/serverless for it's timeout warning, auto-handling of flush, and links to cloudwatch logs
• But this caused all of our performance transaction traces to have an incorrect name (and various other tag + context issues)

Proposal

• A new startTransaction boolean flag that turns on/off the transaction tracing feature of @sentry/serverless
• This will allow our team to use @sentry/serverless, but still rely on express tracingHandler for performance traces
• This also follows the general approach of the serverless package, where each feature is gated by a wrapOptions flag

Alternatives

• We tried various ways to have the express transaction name override the Lambda one, but couldn't get that working
• If there is a way to do that without needing a PR like this, that would be great!

For reviewers

• I'd recommend hiding whitespace when reviewing