-
-
Notifications
You must be signed in to change notification settings - Fork 482
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce a way to easily add a Fingerprint to exceptions like Raven.extra_context #884
Labels
Projects
Comments
any news? 👍 |
since the old however, if you have upgraded to the new SDK, you can do something like this: Sentry.configure_scope do |scope|
scope.set_fingerprint(your_fingerprint)
end # configure fingerprint globally
Sentry.capture_exception(exception)
# or
Sentry.with_scope do |scope|
scope.set_fingerprint(your_fingerprint)
Sentry.capture_exception(exception) # only applies to events sent in the block
end (if you haven't migrated to the new SDK, here's the migration guide that will help you do that 🙂 ) I hope this comment answers your question. I'm closing this now, but feel free to open another issue if the above sample doesn't work. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Use case:
Am re-raising some exceptions, or explicitly raising ones, while calling
Have searched around and found that you can pass a fingerprint to explicitly segregate groups of exceptions on Sentry, which would be amazing to have in a use case we have.
However I could not find any way to do this through anything except
capture_message
orcapture_exception
.Can this be added in like a
Raven.fingerprint_context
or similar as well?If not, how can I currently do this?
Thanks!
The text was updated successfully, but these errors were encountered: