Lukas Stracke

Always happy to refine/discuss this. Since this became a very important issue, we should sync with everyone here who has context on how transaction names/parameterization/routing instrumentation currently works

@smeubank fleshed out the issue description. Feel free to add/change stuff

Hi @jamesbvaughan, would you mind opening a dedicated issue for this? Makes it easier to track this for us. cc @AbhiPrasad maybe you have a quick idea?

Hi @rpanadero and thanks for reporting! Also thanks for the good description. Would you be able to provide a simple reproduction for us to work on this? I don't think...

I took a quick look at the repro and I saw that you're using a custom ErrorHandler. I suspect that one of the reasons for doing this is because you...

Thanks for getting back to me. I agree, this needs a more thorough investigation. Right now though, our priorities are on other tasks but I'll backlog this with high priority....

Hi @woss, thanks for writing in. To me, it seems like `app.use(Sentry.Handlers.tracingHandler())` creates transactions for all incoming requests on `app`. The `Express` integration only adds additional spans to the requests....

Hi @zspitzer and thanks for reporting! This sounds interesting (haven't yet seen a similar error or reports). Would you mind sharing your Sentry setup? For example your Sentry.init, options and...

> I'm willing to put the polyfill back if we decide it's worth the bundle size hit, but given the tiny sliver of end-users this is presumably coming from, I'd...

I'll make sure to document this in a sort of "New SDK release checklist"