Skip to content

Commit a187d77

Browse files
Merge pull request #53 from datum-cloud/chore/update-sentry-ample-rate
chore: don't capture all traces
2 parents 34b5ae3 + 595fd87 commit a187d77

File tree

2 files changed

+4
-2
lines changed

2 files changed

+4
-2
lines changed

apps/login/sentry.server.config.ts

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,9 @@ Sentry.init({
88
dsn: process.env.NEXT_PUBLIC_SENTRY_DSN,
99

1010
// Define how likely traces are sampled. Adjust this value in production, or use tracesSampler for greater control.
11-
tracesSampleRate: 1,
11+
tracesSampleRate: 0.1,
12+
replaysSessionSampleRate: 0.1,
13+
replaysOnErrorSampleRate: 1.0,
1214

1315
// Enable sending user PII (Personally Identifiable Information)
1416
// https://docs.sentry.io/platforms/javascript/guides/nextjs/configuration/options/#sendDefaultPii

apps/login/src/instrumentation-client.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ Sentry.init({
1111
integrations: [Sentry.replayIntegration()],
1212

1313
// Define how likely traces are sampled. Adjust this value in production, or use tracesSampler for greater control.
14-
tracesSampleRate: 1,
14+
tracesSampleRate: 0.1,
1515

1616
// Define how likely Replay events are sampled.
1717
// This sets the sample rate to be 10%. You may want this to be 100% while

0 commit comments

Comments
 (0)