mirror of
https://github.com/supabase/supabase.git
synced 2026-05-09 00:10:05 +08:00
10f49d85f1
## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## What kind of change does this PR introduce? Chore ## What is the current behavior? 100% of traces are being sent to Sentry, which alone would blew through all of our quota leaving no spans available for other projects. For April we are already rate limited. ## What is the new behavior? Change `tracesSampleRate` to more reasonable value (0.02). <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Optimized performance monitoring sampling configuration to reduce application overhead while maintaining essential error tracking and diagnostics. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
27 lines
941 B
TypeScript
27 lines
941 B
TypeScript
// This file configures the initialization of Sentry for edge features (middleware, edge routes, and so on).
|
|
// The config you add here will be used whenever one of the edge features is loaded.
|
|
// Note that this config is unrelated to the Vercel Edge Runtime and is also required when running locally.
|
|
// https://docs.sentry.io/platforms/javascript/guides/nextjs/
|
|
|
|
import * as Sentry from '@sentry/nextjs'
|
|
|
|
Sentry.init({
|
|
dsn: process.env.NEXT_PUBLIC_SENTRY_DSN,
|
|
...(process.env.NEXT_PUBLIC_SENTRY_ENVIRONMENT && {
|
|
environment: process.env.NEXT_PUBLIC_SENTRY_ENVIRONMENT,
|
|
}),
|
|
// Setting this option to true will print useful information to the console while you're setting up Sentry.
|
|
debug: false,
|
|
|
|
// Enable performance monitoring
|
|
tracesSampleRate: 0.02,
|
|
ignoreErrors: [
|
|
'NEXT_NOT_FOUND',
|
|
'NEXT_REDIRECT',
|
|
/504 Gateway Time-out/,
|
|
'Network request failed',
|
|
'Failed to fetch',
|
|
'AbortError',
|
|
],
|
|
})
|