feat: sentry integration (#1020) #1029
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
🤦 fixed. |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds Sentry error tracking integration for client-side error monitoring in the brc-analytics application. The implementation initializes Sentry client-side instrumentation, configures environment-specific DSNs for dev and prod, and sets up a custom error page for Next.js Pages Router. Source map uploads are intentionally disabled as noted in the description.
Key Changes:
- Added
@sentry/nextjsv10.27.0 dependency for error tracking - Configured Sentry initialization in
instrumentation-client.tswith environment-based settings - Created custom error page (
pages/_error.tsx) to capture errors via Sentry - Added DSN configuration in dev/prod environment files
Reviewed changes
Copilot reviewed 7 out of 9 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| instrumentation-client.ts | New file initializing Sentry client-side with DSN and environment configuration |
| pages/_error.tsx | New custom error page capturing errors to Sentry using Pages Router |
| next.config.mjs | Wrapped Next.js config with Sentry, disabled source maps |
| package.json | Added @sentry/nextjs dependency |
| site-config/brc-analytics/{dev,prod}/.env | Added NEXT_PUBLIC_SENTRY_DSN configuration |
| .env | Added example Sentry configuration with documentation |
| .gitignore | Added .env.sentry-build-plugin to ignore list |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
frano-m
approved these changes
Dec 2, 2025
hunterckx
approved these changes
Dec 3, 2025
Contributor
|
@dannon would you mind rebasing this PR so it can be merged thank you! |
Configure via NEXT_PUBLIC_SENTRY_DSN environment variable.
- Remove unneeded server/edge configs (static export) - Remove App Router files (using Pages Router) - Remove example pages - Use env var for DSN instead of hardcoding - Add typed _error.tsx for Pages Router error capture
Not needed for Pages Router projects.
Uses NEXT_PUBLIC_SITE_CONFIG to segment errors by environment.
Add DSN to site-config env files.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adds Sentry error tracking integration for client-side error monitoring.
Configuration:
Implementation:
Related Issue
Closes #1020