Configuring error grouping settings

Default grouping

Airbrake calculates a hash for each error and groups errors with same hash together. The following attributes are used to calculate the hash:

  • error type
  • error message with data fields extracted (see structured logging)
  • function
  • file
  • line
  • environment

Line shifts

Line shifts: When code changes cause an error to occur on a different line in the file, Airbrake will place the error into the existing error group.

This is a common occurrence and handling line shifts as part of error grouping avoids creating duplicate errors and notifications, keeping your error dashboard clean and focused.

Custom grouping

There are a few exceptions where Airbrake uses different data for the hash, these are configured per project from the projects’s settings page.

Global grouping

Create Error Groups by error type, don’t use default grouping rules

Errors added to global grouping will be grouped together by error type, differences in error message, component and action, function, and file will not create new groups.

e.g. errors with the same Error type, and unique values for everything else will be grouped together.

Global grouping compares hashes based on:

  • error type
  • environment

Strict grouping

Create error groups by unique backtrace

A hash is created from the whole backtrace, not only the line where the error occured.

e.g. two errors that are exactly the same except for their backtraces will now create 2 groups instead of ending up in the same group

Strict grouping compares hashes based on:

Table of grouping rules

default global strict
error type used used used
backtrace - - used
error message used - -
function used - used
file used - used
environment used used used

Using these settings

To configure an error group to use a custom grouping setting, first identify the error type:

find error type

Then input that error’s error type in the grouping list you’d like to use and click the “save” button:

input error type

Note: changing grouping settings is not retroactive. ie: existing errors will not be regrouped.

Want to input multiple error types? No problem - just separate entries by newlines.