chore: something wrong with sentry

nodejs · Nov 29, 2023 · 59f3b98 · 59f3b98
1 parent 159be16
commit 59f3b98
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 26 deletions.
diff --git a/sentry.edge.config.ts b/sentry.edge.config.ts
@@ -1,16 +1,5 @@
 import { init } from '@sentry/nextjs';
 
-import {
-  SENTRY_DSN,
-  SENTRY_ENABLE,
-  SENTRY_CAPTURE_RATE,
-} from '@/next.constants.mjs';
+import { SENTRY_DSN, SENTRY_ENABLE } from '@/next.constants.mjs';
 
-init({
-  // Only run Sentry on Vercel Environment
-  enabled: SENTRY_ENABLE,
-  // Provide Sentry's Secret Key
-  dsn: SENTRY_DSN,
-  // Percentage of events to send to Sentry (1% of them) (for performance metrics)
-  tracesSampleRate: SENTRY_CAPTURE_RATE,
-});
+init({ enabled: SENTRY_ENABLE, dsn: SENTRY_DSN });
diff --git a/sentry.server.config.ts b/sentry.server.config.ts
@@ -1,16 +1,5 @@
 import { init } from '@sentry/nextjs';
 
-import {
-  SENTRY_DSN,
-  SENTRY_ENABLE,
-  SENTRY_CAPTURE_RATE,
-} from '@/next.constants.mjs';
+import { SENTRY_DSN, SENTRY_ENABLE } from '@/next.constants.mjs';
 
-init({
-  // Only run Sentry on Vercel Environment
-  enabled: SENTRY_ENABLE,
-  // Provide Sentry's Secret Key
-  dsn: SENTRY_DSN,
-  // Percentage of events to send to Sentry (1% of them) (for performance metrics)
-  tracesSampleRate: SENTRY_CAPTURE_RATE,
-});
+init({ enabled: SENTRY_ENABLE, dsn: SENTRY_DSN });