Due to popular demand, we’ve been working on adding server-side filtering of data. The simple version of this is discarding events from things like browser extensions, but under the hood the goal is to provide a lot more power over time. These apply before rate limits, and are part of a larger shift on our end to allow you to remove unwanted data as much as possible.
Right now we’ve got a few baked in filters (in addition to our already existing IP filters):
- Web crawlers
- Localhost errors (e.g. from development environments)
If you’re running open source Sentry you’ll also be able to create your own filters. Though we’re not willing to commit to a stable API at this point, it’s unlikely to change, or to change much.
Here’s what it looks like today, within your project settings:
We’d love to get more community feedback, and using this as an avenue for that seems ideal. What would you like to see here?