-
Notifications
You must be signed in to change notification settings - Fork 68
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
Question: Usage of add_filter #195
Comments
There's no need to check for |
Will do, thank you. |
Thanks! So what happens is that I am going to reopen this issue because I consider this to be a bug. Library filters should be added before all user filters, which is not happening as of now. To workaround the issue, you could craft the following filter: Airbrake.add_filter do |notice|
if notice.stash[:rack_request]
notice.ignore! if notice.stash[:rack_request].user_agent.match(/BLEXBot/)
end
end |
Fixes #195 (Question: Usage of add_filter) We need to make sure that Airbrake library have higher precedence over user filters to avoid confusion when expected data is not present in the Notice object.
Fixes #195 (Question: Usage of add_filter) We need to make sure that Airbrake library have higher precedence over user filters to avoid confusion when expected data is not present in the Notice object.
Fixes #195 (Question: Usage of add_filter) We need to make sure that Airbrake library have higher precedence over user filters to avoid confusion when expected data is not present in the Notice object.
We have the following snippet in our initializer:
However, errors originating from
BLEXBot
keep appearing in Airbrake. Can you see any problem in the way we use it? Many thanks.The text was updated successfully, but these errors were encountered: