Global Error Classes

Airbrake now allows you to group errors as a "global" error which allows you to group errors that may happen across your application under one error class. For example, if your MySQL server goes down, in a Rails applications the errors will appear from many different controllers and models and clutter your Airbrake dashboard up. By setting the error class for these errors as a global class, the errors will be grouped together as they are delivered to our service.

To enable global error classes for a project, first go to the edit project page:

Screen_Shot_2014-05-09_at_16.01.56.png

Next, fill in the errors you would like grouped together. You can use spaces, newlines, or commas to separate error classes:

Screen_Shot_2014-05-09_at_16.02.54.png

The defaults are

Mysql::Error
MemCache::MemCacheError
Mongrel::TimeoutError
ThinkingSphinx::ConnectionError
Net::HTTPFatalError
OpenURI::HTTPError
ActiveResource::ResourceNotFound
ActiveResource::TimeoutError
ActiveResource::ServerError
Net::SMTPServerBusy
Net::SMTPFatalError
Net::SMTPSyntaxError

For this example we've submitted two errors under the RuntimeError class. From the dashboard we'll only see one entry for that group:

20100623-k4d22i9d89kxkyprbm2km8uiw7.jpeg

As new errors come in, you'll see them under the same group instead of separate:

Screen_shot_2010-06-23_at_3.08.30_PM.png

Screen_shot_2010-06-23_at_3.08.38_PM.png