How can I filter out errors on sentry to avoid consuming my quota?

user_2653437 0
Viewed 3369

I'm using Sentry to log my errors, but there are errors I'm not able to fix (or could not be fixed by me) like

OSError (write error)

enter image description here

Or error that come from RQ (each time I deploy my app)

enter image description here

Or client errors (which are client.errors)

enter image description here

I can't just ignore them because I consume all my quota. How I can filter out this errors?

Here some references for interested people.

sentry uwsgi client filter django
3 Answers
user_50810210
user_59514010

To safe yourself some quota, you have two options:

  1. Avoid forwarding events client side, thus preventing events being send to sentry at all. Have a look at the docs for available client-side filters. The drawback with this approach is of course that you need a new code deployment for any adjustment of client-side filters and some clients may not instantly reflect your code changes.
  2. Avoid forwarding events on sentry's side, via inbound filters ([Project] > Project Settings > Inbound Filters). According to the sentry documentation on quota usage, events filtered via inbound filters are not affecting your quota.

Inbound filters include:

  • Common browser extension errors
  • Events coming from localhost
  • Known legacy browsers errors
  • Known web crawlers
  • By their error message
  • From specific release versions of your code
  • From certain IP addresses

Business plans and above also allow to filter events by error messages.

user_24776190
Related