feat(telemetry): implement glitchtip/sentry integration with smart proxy
Some checks failed
Build & Deploy / 🔍 Prepare (push) Successful in 10s
Build & Deploy / 🧪 QA (push) Failing after 2m43s
Build & Deploy / 🏗️ Build (push) Failing after 5m34s
Build & Deploy / 🚀 Deploy (push) Has been skipped
Build & Deploy / 🩺 Health Check (push) Has been skipped
Build & Deploy / 🔔 Notify (push) Successful in 2s
Some checks failed
Build & Deploy / 🔍 Prepare (push) Successful in 10s
Build & Deploy / 🧪 QA (push) Failing after 2m43s
Build & Deploy / 🏗️ Build (push) Failing after 5m34s
Build & Deploy / 🚀 Deploy (push) Has been skipped
Build & Deploy / 🩺 Health Check (push) Has been skipped
Build & Deploy / 🔔 Notify (push) Successful in 2s
- Added Sentry/GlitchTip relay route handler - Configured Sentry for client (with tunnel), server, and edge runtimes - Refactored GlitchTip adapter to use official @sentry/nextjs SDK - Fixed ComparisonRow type issues and Analytics Suspense bailout - Integrated Sentry instrumentation into the boot sequence
This commit is contained in:
16
apps/web/sentry.client.config.ts
Normal file
16
apps/web/sentry.client.config.ts
Normal file
@@ -0,0 +1,16 @@
|
||||
import * as Sentry from "@sentry/nextjs";
|
||||
|
||||
// Use a placeholder DSN on the client as the real one is injected by our relay
|
||||
const CLIENT_DSN = "https://public@errors.infra.mintel.me/1";
|
||||
|
||||
Sentry.init({
|
||||
dsn: CLIENT_DSN,
|
||||
// Relay events through our own server to hide the real DSN and bypass ad-blockers
|
||||
tunnel: "/errors/api/relay",
|
||||
|
||||
enabled: true,
|
||||
|
||||
tracesSampleRate: 0,
|
||||
replaysOnErrorSampleRate: 1.0,
|
||||
replaysSessionSampleRate: 0.1,
|
||||
});
|
||||
Reference in New Issue
Block a user