-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Disable sentry-trace headers #12302
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
Hey, the thing that controls the headers is With the config you set, sentry-trace header would be attached to any URL matching "example.com". Just to be clear, are you talking about |
I have tried both configurations with no success. Here is my current config. I removed the
Note that previously I was using
|
Hey, can you try just removing all trace sample rates completely, we handle it slightly different if it is defined vs. not defined. Sentry.init({
dsn: "https://xxxxx.ingest.sentry.io/xxxxx",
sampleRate: 0,
autoSessionTracking: false,
tracePropagationTargets: [],
}); Does that work? |
That worked. Merci! |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/browser
SDK Version
8.5.0
Framework Version
2.5.10
Link to Sentry event
No response
SDK Setup
Steps to Reproduce
See above code
Expected Result
Sentry should simply be processing server exceptions and logging them. No other 'features' should be enabled.
Actual Result
I am trying to use Sentry to capture server errors but I don't know how to prevent it from just taking over. It's adding sentry-trace and baggage headers to HTML pages, and there seems to be no way to disable it. Things seem opt-out when they should be opt-in.
From what I can tell the tracePropagationTargets setting should allow me to disable it, but it doesn't seem to work. I've set tracePropagationTargets to example.com but it's still sending out those headers with all requests.
I am caching my HTML pages at the edge which would probably make these headers useless anyways.
Another user brought up a similar issue before.
The text was updated successfully, but these errors were encountered: