admin
7dde951306
- Added Sentry configuration for edge features in `sentry.edge.config.ts` - Added Sentry configuration for server-side in `sentry.server.config.ts` - Created a sample API route to demonstrate error tracking in `src/app/api/sentry-example-api/route.ts` - Developed a frontend page to trigger and log errors in `src/app/sentry-example-page/page.tsx` - Configured client-side Sentry initialization in `src/instrumentation-client.ts` with Replay integration - Implemented instrumentation registration logic in `src/instrumentation.ts`
21 lines
926 B
TypeScript
21 lines
926 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: "https://a9390ae6d4b06c851854d48b070bb4cf@o4511511166713856.ingest.us.sentry.io/4511612532228096",
|
|
|
|
// Define how likely traces are sampled. Adjust this value in production, or use tracesSampler for greater control.
|
|
tracesSampleRate: 1,
|
|
|
|
// Enable logs to be sent to Sentry
|
|
enableLogs: true,
|
|
|
|
// Enable sending user PII (Personally Identifiable Information)
|
|
// https://docs.sentry.io/platforms/javascript/guides/nextjs/configuration/options/#sendDefaultPii
|
|
sendDefaultPii: true,
|
|
});
|