Airbrake has been used by other teams in my organizations for quite some time. My team and I were building a new Rails application and we decided to include Airbrake for error reporting. Using Airbrake was one of the best decisions we made and here's why: tl;dr - Installation, configuration, and integration were all painless. My only request is to expand supported integrations to more and different systems (New Relic, in our case). 1) App integration: "Installing" Airbrake in our Rails application was as simple as adding an entry in our Gemfile and creating an initializer for configuration. And that's it! 2) Configurability: As I just mentioned, configuration is available in your application. However, configuration "points" also exist in Airbrake at the account, project, and user levels. All these configurations work together seamlessly. This has allowed us to get the right notifications to the right people at the right time and avoid the "notification overload" that can come with other monitoring solutions. 3) External Integrations: Airbrake supports integration with many popular issue trackers and team communication solutions. We integrate Airbrake with JIRA and Slack, so there was no need to introduce a new tool to our daily workflow. However, I would like to see integration support expanded. For example, the integration with New Relic requires a third party solution that ended up not working for us. Airbrake does support webhooks, so we're still able to integrate with systems that are not supported OoTB. 4) Documentation: Setting up Airbrake and integrating it into our ecosystem has required little to no guesswork on our part.

We rely on Airbrake for additional production and test environment monitoring of app exceptions. By linking Airbrake error alerts to HipChat notifications, we get great high-level alerts whenever an error happens, right in our team chat room. It's easy to drill down into the error details with the UI. We also use the Comments feature of the Airbrake errors to reduce bystander effect among team members -- no comment means nobody triaged the issue.

Airbrake is easy to use, the pricing is great, and the granularity of the information is good as well.

We used Airbrake for many years and found it easy to integrate it into projects with Ruby on Rails and other popular frameworks. Over time the company has shifted more towards using Rollbar which is compatible with Airbrake clients but had more advanced server side aggregation of errors and other search / filtering features that came in handy for us.

since we don't have the luxury of time to debug and traceback every issue happening to our multiple sites, airbrake cuts so much time debugging and that time saved is better spent on working on a fix right away, sometimes even before the users notice anything.