SvelteKit Tracing

[hlesmana-var]

Hello,

I'm trying to learn more about tracing works out of the box with BrowserTracing integration. Specifically, how does sentry-trace header gets passed by the SDK (@sentry/sveltekit) from the client side to server side (SvelteKit fetch).

e.g if I have the below routes and /home is making fetch to GET /api/test

/home/+page.svelte 
/api/test/+server.js 

In the above, should I be seeing the sentry-trace http header on the GET /api/test? My expectation is that the header would be there to tie the client and server together. I couldn't seem to find the header (e.g. on chrome dev tool).

[AbhiPrasad]

Hey @hlesmana-var - the SDK uses the tracePropagationTargets field to decide what requests to attach headers to.

Sentry.init({
  dsn: "PUBLIC_DSN",
  // Set `tracePropagationTargets` to control for which URLs trace propagation should be enabled
  tracePropagationTargets: ["localhost", /^https:\/\/yourserver\.io\/api/],
});

[hlesmana-var]

Got it. So there shouldn't be any difference between Sveltekit's fetch and native fetch. i.e. sentry-trace and baggage should be in the header, if the SDK is configured correctly.

[AbhiPrasad]

No difference at all to the SDK between sveltekit fetch and native fetch.

[hlesmana-var]

Thanks, I think my issue was with the sample rate and/or quota.