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

ability to set a global reporting level #1793

Closed
modosc opened this issue Apr 18, 2022 · 1 comment
Closed

ability to set a global reporting level #1793

modosc opened this issue Apr 18, 2022 · 1 comment

Comments

@modosc
Copy link
Contributor

modosc commented Apr 18, 2022

it would be useful to configure a global exception reporting level (eg, :warning, :error) so that all reported exceptions below this level are dropped.

rollbar/bugsnag have this afaik.

the only way i could find to do this was via before_send but we found the structures passed into that method don't match the structures in the docs and we couldn't find a reliable way to filter on level:.

@github-actions
Copy link

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!


"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

sl0thentr0py added a commit that referenced this issue Oct 22, 2024
The change in #1793 accidentally exposed params always in the controller action span.
This change now respects both `Rails.config.filter_parameters` and `Sentry.coniguration.send_default_pii`
together to decide what to send.
sl0thentr0py added a commit that referenced this issue Oct 22, 2024
The change in #1793 accidentally exposed params always in the controller action span.
This change now respects both `Rails.config.filter_parameters` and `Sentry.coniguration.send_default_pii`
together to decide what to send.
sl0thentr0py added a commit that referenced this issue Oct 22, 2024
The change in #1793 accidentally exposed params always in the controller action span.
This change now respects both `Rails.config.filter_parameters` and `Sentry.coniguration.send_default_pii`
together to decide what to send.
sl0thentr0py added a commit that referenced this issue Oct 22, 2024
The change in #1793 accidentally exposed params always in the controller action span.
This change now respects both `Rails.config.filter_parameters` and `Sentry.coniguration.send_default_pii`
together to decide what to send.
@sl0thentr0py sl0thentr0py closed this as not planned Won't fix, can't repro, duplicate, stale Dec 10, 2024
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

4 participants