-
Notifications
You must be signed in to change notification settings - Fork 327
chore: reduce Sentry span sampling outside development #1475
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -15,7 +15,7 @@ if (!!process.env.NEXT_PUBLIC_SENTRY_WEBAPP_DSN && !!process.env.NEXT_PUBLIC_SEN | |
| integrations: [ | ||
| Sentry.browserProfilingIntegration(), | ||
| ], | ||
| tracesSampleRate: 1.0, | ||
| tracesSampleRate: process.env.NEXT_PUBLIC_SENTRY_ENVIRONMENT === 'development' ? 1.0 : 0.1, | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Dev sampling env mismatchMedium Severity The Reviewed by Cursor Bugbot for commit af8c811. Configure here. |
||
| // Evaluated once per `Sentry.init()`, i.e. once per page load. | ||
| profileSessionSampleRate: 1.0, | ||
| // Profile only while a sampled root span is active, rather than continuously. | ||
|
|
||


There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wrong Sentry sampling option
High Severity
The change intended to sample Sentry error events at 10% outside development. Instead,
tracesSampleRatewas modified, leaving error capture at 100%. This samples web traces and associated profiling at 10% (instead of 100%) and newly enables backend performance tracing.Reviewed by Cursor Bugbot for commit af8c811. Configure here.