You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we capture exceptions, we are sending them to our Exception Handler.
Backend: See ExceptionHandlerService / captureException
Frontend: See SentryInitEffect
These errors are sent to Sentry in production. They are working fine but we would like to know which user (and on which workspace) the error has been triggered. We would like to add user_id, workspaceMember_id, workspace_id to this payload when they are available (obviously if an error happens while the user is logged out, we cannot send them)
Technical inputs
See: https://develop.sentry.dev/sdk/event-payloads/user/
On the BE, the user information should be computed based on JWT token. Exceptions are handled here: global-exception-handler.util.ts. I am not sure about the best way to properly make the user availalble in this file, we might have to rather pass it as a parameter of globalExceptionHandler when we call it from GraphQLConfigService for example. See all the services calling globalExceptionHandler, we should make sure the user is passed in all cases
On the FE side, the user information is available in currentUser, currentWorkspace and currentWorkspaceMember states
The text was updated successfully, but these errors were encountered:
Scope & Context
When we capture exceptions, we are sending them to our Exception Handler.
ExceptionHandlerService
/captureException
SentryInitEffect
These errors are sent to Sentry in production. They are working fine but we would like to know which user (and on which workspace) the error has been triggered. We would like to add user_id, workspaceMember_id, workspace_id to this payload when they are available (obviously if an error happens while the user is logged out, we cannot send them)
Technical inputs
See: https://develop.sentry.dev/sdk/event-payloads/user/
On the BE, the user information should be computed based on JWT token. Exceptions are handled here:
global-exception-handler.util.ts
. I am not sure about the best way to properly make the user availalble in this file, we might have to rather pass it as a parameter ofglobalExceptionHandler
when we call it fromGraphQLConfigService
for example. See all the services callingglobalExceptionHandler
, we should make sure the user is passed in all casesOn the FE side, the user information is available in currentUser, currentWorkspace and currentWorkspaceMember states
The text was updated successfully, but these errors were encountered: