Inbound Filters

Inbound Crash Report filtering for Raygun

Inbound Filters for Raygun Crash Reporting allow you to filter out errors before they are recorded in Raygun, keeping them from being counted against your monthly limit.

Jump to an item:

Inbound filters location

To start setting up Inbound Filters click on "Filtering" under the Crash Reporting option in the left navigation sidebar in Raygun. 

The Inbound Filter screen is divided into two sections:  "Create an inbound filter" and "Active inbound filters"

The "Create an inbound filter" section allows you to specify new inbound filters you want to add for this application.  "Active inbound filters" shows you which inbound filters you have available and which inbound filters are currently active.

Creating inbound filters

When creating a new inbound filter you can choose between several different filter types:

Note: Wildcards (*) are supported for all inbound filter types. New inbound filters are NOT applied to currently stored exceptions, only to incoming exceptions after the inbound filters are created/activated.

IP address

To create an IP Address inbound filter, enter in the IP Address of the resource you want to filter out.

Wildcard example: 192.168.0.* will match any address with the first three segments

Machine name

To create a Machine Name inbound filter, enter in the machine name of the resource(s) that you want to prevent exceptions being tracked for.

Wildcard example: *PC will match any machine name ending with PC

HTTP -  Hostname or URL path

To create an HTTP inbound filter, choose to discard requests from the Hostname or URL path, then enter in the Hostname or URL path you want exceptions to be filtered out for.


Wildcard example: * will match any sub-domain of

Additionally, while not part of the hostname, you can also filter on the protocol here. Example: file://*

URL paths

Wildcard example: */signin will match any paths ending in /signin

Version - Number or Build number

To create a Version inbound filter, enter in the version number you want exceptions to be filtered out for.

Additionally, using the drop-down menu, you can set a comparison operator for the version from the following list:

  • Equal to
  • Not equal to
  • Greater than
  • Greater than or equal to
  • Less than
  • Less than or equal to
  • Not found

Wildcard example: 2.* will match any any version in the 2 range

Errors with no specific version

To create an inbound filter select for errors with no specific version, choose "Version" and "Not found" from the drop-down menu:

Error message

To create a Message inbound filter enter in the string you want to filter out for.  The strings are not case sensitive so rayGUN will match both raygun and RAYGUN.

Wildcard examples: HttpException* will match any messages starting with HttpException, while *HttpException* will match any messages containing HttpException.


To create a Tag inbound filter enter in the tag name you want to filter out.  The tag names are not case sensitive so mYtAg will match both mytag and MyTag.

Wildcard example:  MyTag* will match any tags starting with MyTag

User agent

To create a user agent inbound filter enter in the name of the user agent you want to filter out.  The names are not case sensitive

Wildcard example: Mozilla/5.0*

Active inbound filters

The top portion of the Active Filters section shows the inbound filters that have been created in the "Create a filter" section.

Provider filters

The bottom portion of the Active Filters section displays the Provider Filters which are supplied by Raygun.  These inbound filters are built and can be turned off and on by clicking on the button sliders located on the far right side of the individual filters.

Once activated, the individual inbound filter's "Date added" field will update with the current date.  If the inbound filter is deactivated the "Date added" value will be cleared.

The currently available Provider Filters are:

  • ?Discard any requests where the user-agent is a known crawler bot
  • Discard any requests for non existent resources (404)
  • Discard any requests where the host is a .local domain or is localhost
  • Discard any requests related to phpMyAdmin access attempts
  • ASP.NET: Discard any requests which failed request validation - e.g. XSS attempts
  • JavaScript: Discard any errors where no information is available due to browser security restrictions

Documentation missing?

If we don't have documentation about your desired topic, send us a message and we'll create it for you.