quivr/frontend/sentry.client.config.ts
Stan Girard 0e5f5d887a
fix: Update Sentry configuration to use NEXT_PUBLIC_SENTRY_DSN (#2254)
This pull request updates the Sentry configuration to use the
`NEXT_PUBLIC_SENTRY_DSN` environment variable instead of `SENTRY_DSN`.
This ensures that the correct DSN is used for Sentry initialization.
2024-02-23 18:12:50 -08:00

40 lines
1.3 KiB
TypeScript

// This file configures the initialization of Sentry on the client.
// The config you add here will be used whenever a users loads a page in their browser.
// https://docs.sentry.io/platforms/javascript/guides/nextjs/
import * as Sentry from "@sentry/nextjs";
// Get the DSN from the environment variable
const SENTRY_DSN = process.env.NEXT_PUBLIC_SENTRY_DSN;
// Only initialize Sentry if the DSN is set
if (SENTRY_DSN) {
Sentry.init({
dsn: SENTRY_DSN,
// Adjust this value in production, or use tracesSampler for greater control
sampleRate: 0.1,
tracesSampleRate: 0.1,
// Setting this option to true will print useful information to the console while you're setting up Sentry.
debug: false,
replaysOnErrorSampleRate: 0.1,
// This sets the sample rate to be 10%. You may want this to be 100% while
// in development and sample at a lower rate in production
replaysSessionSampleRate: 0.1,
// You can remove this option if you're not planning to use the Sentry Session Replay feature:
integrations: [
new Sentry.Replay({
// Additional Replay configuration goes in here, for example:
maskAllText: true,
blockAllMedia: true,
}),
],
});
} else {
console.log("Sentry is not initialized as SENTRY_DSN is not set");
}