Disable Sentry performance tracing on brios - #2371
Merged
Merged
Conversation
Keep error monitoring (DSN, onRequestError, captureRouterTransitionStart). Set tracesSampleRate to 0 on client, server, and edge so /sites browser spans (http.client, resource.img/script) are no longer ingested. Co-authored-by: Brian Lovin <brianlovin@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
brianlovin
marked this pull request as ready for review
September 16, 2026 19:55
brianlovin
deleted the
cursor/disable-sentry-performance-tracing-a132
branch
September 16, 2026 19:55
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The Sentry org is at ~80% reserved spans. The
briosproject (brianlovin.com) is about half of that volume. Browser tracing on/sitesalone was ~1.64M spans in the last 14 days (http.client,resource.img,resource.script).Brian does not use performance spans for this site. Error monitoring should stay on.
What
Set
tracesSampleRatefrom1to0in all three Sentry init configs:instrumentation-client.ts(browser)sentry.server.config.ts(Node)sentry.edge.config.ts(edge / middleware)0means this app does not sample its own traces, so/sitesbrowser spans stop being ingested. There is no separatebrowserTracingIntegration,enableLogs, resource-span, or HTTP client span config in this repo that would keep emitting performance spans.Left intact:
captureException/withErrorCapture)onRequestError(Sentry.captureRequestError)captureRouterTransitionStart(kept; with sample rate0it does not ingest performance spans for this site's own navigations)Testing
tracesSampleRateassignments are now0, and DSN / error hooks remain@sentry/coresampleSpan({ tracesSampleRate: 0 }, …)returnssampled: falsebun run lintpassedbun run buildpassed (Next.js 16.3.0; compiled + TypeScript + 68/68 pages)