Un-noted breaking change of ^7.97.0 (tracing)? #10490

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/browser

SDK Version

7.99.0

Framework Version

Angular 17.1.1

Link to Sentry event

No response

SDK Setup

  Sentry.init({
    dsn,
    environment,
    release,
    beforeBreadcrumb(breadcrumb, hint) {
      // <some custom formatting>
      return breadcrumb;
    },
    beforeSend(event) {
      // <some manual exclusions>
      return event;
    },
    ignoreErrors: [
      // <something here>
    ],
    denyUrls: [
      // <something here>
    ],
    integrations: [
      new Sentry.BrowserTracing(),
    ],
    tracesSampleRate: 0.02
  });

Steps to Reproduce

Starting with ^7.97.0 our tracing capture rate increased by ~1200% = 12x which almost have eaten all of our transactions quota 🫠

Digging into what have changed I've noticed a lot of separate http requests being recorded as separate transactions. In the transactions table of performance page a bunch of entries with operation http.client have appeared. Basically, every single "ajax" call (including all 3rd party targets) is being recorded now as a separate transaction.

This was not happening with 7.95.0 (and older versions).

I believe, this 52495c0 introduced the change.

Expected Result

Was this change really intentional?

Actual Result

.