Skip to content
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

Closed
parreirat opened this issue Jan 24, 2019 · 2 comments
Projects

Comments

@parreirat
Copy link

Use case:

Am re-raising some exceptions, or explicitly raising ones, while calling

Raven.extra_context
Raven.tags_context
Raven.user_context

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 or capture_exception.

Can this be added in like a Raven.fingerprint_context or similar as well?
If not, how can I currently do this?

Thanks!

@pedrofurtado
Copy link

any news? 👍

@st0012 st0012 added this to the 4.0.0 milestone Aug 27, 2020
@st0012 st0012 added this to To do in 4.x via automation Aug 27, 2020
@st0012 st0012 modified the milestones: 4.0.0, 4.1.0, 4.2.0 Dec 10, 2020
@st0012
Copy link
Collaborator

st0012 commented Dec 18, 2020

since the old sentry-raven gem has entered maintenance mode, we won't add this method to it.

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.

@st0012 st0012 closed this as completed Dec 18, 2020
4.x automation moved this from To do to Done Dec 18, 2020
@st0012 st0012 removed this from the 4.2.0 milestone Dec 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
4.x
  
Done
Development

No branches or pull requests

3 participants