Integrate Sentry error tracking with source‑map upload and PII protec…#406
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
This pr closes #378
Description: This PR adds comprehensive Sentry integration to the Hunty project:
Initialized Sentry on both client and server with DSN support.
Wrapped the root layout in Sentry.ErrorBoundary for UI‑level crash reporting.
Added Sentry.captureException in all Soroban contract calls to report backend errors.
2. Privacy Safeguards
Stripped wallet addresses from Sentry tags and extra data to avoid PII leakage.
3. Source‑Map Upload
Configured Next.js to upload source maps via withSentryConfig for meaningful stack traces in production.
4. Environment
Updated .env.example with SENTRY_DSN placeholder.
All changes are limited to the error‑tracking scope without affecting existing functionality.