Frontend and backend service is not connected with One trace-id value

[deepanshutripathi]

We like to enable distributed tracing in our environment. But our frontend and backend applications is having different trace-id values, for the calls that which frontend makes to backend APIs, due to which in Trace-View, we don't see any connected service and are unable to debug the performance and get complete trace view
We have performed the changes in our code, as per the Doc: https://docs.sentry.io/platforms/javascript/performance/connect-services/#pageload, but still, the issue persists.

We have initialized the Sentry using the below and using "@sentry/tracing": "^7.20.0", "@sentry/vue": "^7.20.0", package + version

  Sentry.init({
    Vue,
    dsn: config?.server?.sentryDsn,
    environment: 'development',
    integrations: [
      new BrowserTracing({
        routingInstrumentation: Sentry.vueRouterInstrumentation(router),
        tracePropagationTargets: ["<our_domain>/api/*", "http://localhost:9090/api/debug-sentry"],
        tracingOrigins: ["localhost", "<our_domain_name>.com"]
      })
    ],
    tracesSampleRate: 1.0,
    maxValueLength: 5000
  });

[lforst]

Hi, tracePropagationTargets doesn't support globbing. "<our_domain>/api/*" should be "<our_domain>/api/". You can verify that requests are getting traced by looking for a baggage or sentry-trace header on the request.

[deepanshutripathi]

Thanks @lforst , let me correct the targets value and update