-
Notifications
You must be signed in to change notification settings - Fork 9
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
chore: Upgrade to sentry-ruby, rails, sidekiq sdks, removes sentry-raven #1537
base: main
Are you sure you want to change the base?
Conversation
config.dsn = Convection.config.sentry_dsn if Convection.config.sentry_dsn | ||
config.processors -= [Raven::Processor::PostData] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If Im reading the migration docs right, I think this is OK to remove as these processors are no longer used in the sdk and there's default data scrubbing behaviors
https://docs.sentry.io/platforms/ruby/migration/#removed-processors
Raven.user_context(id: @current_user) | ||
def set_sentry_context | ||
# Heads up! @current_user is the user's id as a string not an object | ||
Sentry.set_user(user_id: @current_user) | ||
end |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Didnt want to mess with @current_user
at this time - it is used everywhere
and its technically a STRING and not an object - bit of a gotcha when I was testing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!! 🎉
Attempt to get us off of deprecated
sentry-raven
gem, installssentry-ruby
,sentry-rails
,sentry-sidekiq