Feature Release: Save Your Error Quota With Inbound Filters

By Freyja Spaven | Posted Aug 3, 2016 | 2 min. (364 words)

One of the most frequently asked questions here at Raygun is:

How do I reduce my error quota?

(For our top 6 tips on reducing your error quota head to this blog post)

We know it’s inevitable that when you create a new feature or version, there will be bugs.

With Raygun Crash Reporting, as a user, you’ll know that when an error gets picked up, it’s automatically sent into the ‘Active’ tab.

Firstly, the Raygun Dashboard gives a complete overview of what’s happening in your app. The errors can then be moved to be ‘resolved’ or ‘permanently ignored’ as you see fit.

However, what about if you are consistently releasing features? In this case, bugs are inevitable and aren’t necessarily high alert.

To stop these errors being counted against your quota, Raygun has introduced our latest feature:

Inbound Filters

You can now create criteria to ignore errors coming from a specific IP address, machine name, HTTP hostname or URL path, version, error message, tag or user agent.

To make things simple, we’ve also included a quick list of the most requested inbound filters that you can simply toggle on and off as needed.

You can now stop worrying about errors coming from legacy versions going against your company’s cap. By filtering them out, they won’t count towards the final error quota.

Inbound filters are a new feature available to all plans. Follow the instructions below to set up inbound filters:

(Note: You can create multiple inbound filter criteria. If the error matches any of the criteria, Raygun will discard it. Great if you have one member of your team working on a new version release.)