feat: Sentry user context integration with error handling#1076
Merged
Conversation
3 tasks
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
…cumentation Co-authored-by: egelhaus <156946629+egelhaus@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Implement user implementation for Sentry integration
feat: Sentry user context integration with error handling
Nov 24, 2025
egelhaus
requested changes
Nov 24, 2025
| Sentry.setTag('user.super_admin', null); | ||
| try { | ||
| Sentry.setUser(null); | ||
| Sentry.setTag('user.activated', ''); |
Co-authored-by: egelhaus <156946629+egelhaus@users.noreply.github.com>
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
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.
What kind of change does this PR introduce?
Feature - Sentry user context integration for error tracking across frontend and backend.
Why was this change needed?
Associates user information with Sentry error reports to improve debugging and issue triage. When errors occur, Sentry will now show which user was affected along with relevant metadata (org, role, tier).
Changes:
setSentryUserContextandclearSentryUserContextutilities for both React (frontend) and NestJS (backend)SentryUserInterceptorfor automatic backend request context settingContextWrappercomponent via useEffectnullfor tag clearing in both frontend and backendNEXT_PUBLIC_SENTRY_DSNin.env.exampleUsage (backend):
Other information:
The interceptor is provided but not globally registered - teams can choose their preferred integration level (global, controller, or method).
Checklist:
Put a "X" in the boxes below to indicate you have followed the checklist;
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.