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
{{ message }}
This repository has been archived by the owner on Oct 23, 2023. It is now read-only.
As implemented in #686 non-zero SystemExit exceptions are now raised to Sentry. We have an issue that as they all have completely different stack traces they all cause a new individual entry. Is there a way to easily group them in our code? I couldn't work out from the fingerprints if this was achievable?
The text was updated successfully, but these errors were encountered:
wmonk
changed the title
Group SystemExits properly
Group SystemExit exceptions properly
Aug 14, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As implemented in #686 non-zero
SystemExit
exceptions are now raised to Sentry. We have an issue that as they all have completely different stack traces they all cause a new individual entry. Is there a way to easily group them in our code? I couldn't work out from the fingerprints if this was achievable?The text was updated successfully, but these errors were encountered: