feat: add Sentry error monitoring to frontend#260
Open
Javiershenbc wants to merge 1 commit into
Open
Conversation
Upgrade @sentry/react v5 to v10 and complete the frontend integration (errors-only, no performance tracing or session replay). - init moved to src/instrument.ts with sendDefaultPii disabled; browser events routed same-origin through a /tunnel endpoint to avoid ad-blockers - wrap the app in Sentry.ErrorBoundary and report errors from the shared ErrorComponent (covers the route-level errorComponent usages) - capture network and 5xx errors in the axios response interceptor - attach the MSAL user id via Sentry.setUser (no email/IP) - generate hidden sourcemaps and upload them to the self-hosted Sentry via @sentry/vite-plugin, deleting the .map files after upload - add backend POST /tunnel endpoint + SENTRY_TUNNEL_HOST setting to forward envelopes to the Sentry server - thread Sentry build args/secrets through Dockerfile.prod and Azure pipeline
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
1 participant
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.
Upgrade @sentry/react v5 to v10 and complete the frontend integration (errors-only, no performance tracing or session replay).
init moved to src/instrument.ts with sendDefaultPii disabled; browser events routed same-origin through a /tunnel endpoint to avoid ad-blockers
wrap the app in Sentry.ErrorBoundary and report errors from the shared ErrorComponent (covers the route-level errorComponent usages)
capture network and 5xx errors in the axios response interceptor
attach the MSAL user id via Sentry.setUser (no email/IP)
generate hidden sourcemaps and upload them to the self-hosted Sentry via @sentry/vite-plugin, deleting the .map files after upload
add backend POST /tunnel endpoint + SENTRY_TUNNEL_HOST setting to forward envelopes to the Sentry server
thread Sentry build args/secrets through Dockerfile.prod and Azure pipeline