-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
The sentry-trace header is not being sent with fetch requests #3547
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
There has to be an active transaction in order for |
Hi Taylor, have you managed to find a solution? |
Hey @bzeskis, yes this can be closed! |
@taylorlapeyre do you mind sharing you solution? Currently struggling with same :) Pageload metrics are being sent, but later on XHR/Fetch requests are not. |
I'm having the same issue. I cannot find documentation that explains how I can configure sentry to keep tracing after the initial pageload. Sentry.init({
Vue,
dsn: config.api.sentry.dsn,
integrations: [
new Integrations.BrowserTracing({
routingInstrumentation: Sentry.vueRouterInstrumentation(router),
tracingOrigins: [config.hosts.com, config.services.api.host],
}),
],
tracesSampleRate: 1.0,
}) When I look at the options in BrowserTracing, it implies that it will generate a new transaction automatically on each URL change, and that each transaction lasts at most 1 second. However, only the very first API request will get a Update: I found out the issue in my case is not 'first' vs 'subsequent' requests. My first request was done with In short, there's an issue with tracing using |
Potentially related issue: #4439 |
Example event: https://sentry.io/organizations/project-wren/issues/2399314422/events/85d536082ab64b56bf22835c708d986f/
Package + Version
@sentry/browser
: "^1.4.9",@sentry/node
: "^6.3.5"@sentry/tracing
: ""^6.3.5""raven-js
raven-node
(raven for node)Version:
Description
It seems like the
sentry-trace
header is not being sent in fetch requests that we send from our app's frontend. We construct our requests this way:We aren't seeing any distributed tracing for our backend service for requests being initiated this way, and the sentry header is not present:
Our Sentry init:
The text was updated successfully, but these errors were encountered: