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

Rails integration should respect config.filter_parameters #39

Closed
jfirebaugh opened this issue Nov 7, 2012 · 5 comments
Closed

Rails integration should respect config.filter_parameters #39

jfirebaugh opened this issue Nov 7, 2012 · 5 comments

Comments

@jfirebaugh
Copy link
Contributor

filter_parameters is the Rails interface to avoid logging sensitive parameters. raven-ruby's Rails integration should integrate it with the data sanitizer.

@dbwinger
Copy link

dbwinger commented Mar 2, 2013

+1 for this! Out of curiousity have you rolled your own solution for this, @jfirebaugh ? If so would you mind sharing it?

@jfirebaugh
Copy link
Contributor Author

I just relied on the default behavior of Raven::Processor::SanitizeData.

@nathany
Copy link

nathany commented Apr 17, 2013

👍 It would make it at lot easier to filter out CVCs/CVDs and such, right now it involves copying and tweaking SanitizeData. For those not using Rails, the default sanitizer should be easier to configure, which should make the Rails integration straight-forward.

@nateberkopec
Copy link
Contributor

Raven.configure do |config|
  config.sanitize_fields = Rails.application.config.filter_parameters.map(&:to_s)
end

@cooperka
Copy link

Update in 2020: the new sentry-rails v4 no longer supports config.sanitize_fields. After some headaches looking for upgrade documentation, it turns out Sentry handles much filtering automatically so you can probably remove the setting entirely and be on your way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants