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
We want to make it more clear how Sentry is transforming error payloads, specifically for react minified errors. This is because it can be hard to tell how to filter these errors (using either beforeSend or server-side inbound filters) as the UI shows the transformed message, not the original one.
To address this, let's set the _meta field on processed events to add a remark that states that a substitution happened to the exception value. With this field, the UI can then explain to users how to filter errors.
Problem Statement
We want to make it more clear how Sentry is transforming error payloads, specifically for react minified errors. This is because it can be hard to tell how to filter these errors (using either
beforeSend
or server-side inbound filters) as the UI shows the transformed message, not the original one.https://github.com/getsentry/relay/blob/master/relay-general/src/types/meta.rs
https://github.com/getsentry/sentry/blob/master/src/sentry/lang/javascript/errormapping.py
Solution Brainstorm
To address this, let's set the
_meta
field on processed events to add a remark that states that a substitution happened to the exception value. With this field, the UI can then explain to users how to filter errors.add_remark
functionality to Meta class #44884Add message to event details page on how to use_meta
The text was updated successfully, but these errors were encountered: