I work on a single-man project which requires frequent rush-to-production feature changes. Airbrake keeps me on top of my users' problems and allows me to trace their errors. It makes error-tracking simple, and I'm extremely grateful for it being integrated into Heroku for ease of use with my ...Read the full review
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, ...Read the full review
30-day free trial.
Three level of subscription plans available:
Small - $39 per month for 5 applications and 10 users.
Pro - $89 per month for 15 applications and 20 users.
Enterprise - $199 per month for 40 applications and 30 users.
Custom packages are also available on enquiry
I work on a single-man project which requires frequent rush-to-production feature changes. Airbrake keeps me on top of my users' problems and allows me to trace their errors. It makes error-tracking simple, and I'm extremely grateful for it being integrated into Heroku for ease of use with my Rails project. Would definitely use it again and recommend it to others.
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.
I've been using Airbrake for a while and it's a great bug tracker. It facilitates my workflow a lot by getting a lot of info in the email then if I need more I go to the app and figure out the details. It´s great
Airbrake is a valuable tool that is typically used on traffic-heavy applications. The major benefit of Airbrake is it provides extremely detailed exception information. It also has a great visual tool for trending and the functionality to pinpoint a problem to a specific deploy. The readme documentation and open/closed issues on Github accurately reflects the tool. I recommend the Airbrake library to everyone.
We have been using airbrake for almost 5 years now and couldn't be more satisfied. Every exception that is thrown in production gets duly reported to our Slack channel and can be reacted upon. What more can anyone want.
We use Airbrake in a Ruby on Rails app which was super easy to setup and get running. Airbrake has given our IT a proactive capability allowing us to many times get a head of the curve when it comes to knowing about system errors. It has been my experience in the past in many different IT organizations to not find out about an error until the customer reports it. With Airbrake in many instances we were able to get a fix in place and deployed within minutes as opposed to days or hours from the 1st occurrence of a particular error/bug.
It's awesome! Pretty easy to use and setup. Love the Slack integration. Our business lives and Slack and speeds up communication for our operations between business and IT. Also love the Trello integration because Trello is where we track our bugs.
One you changed the user interface on me and it took me a minute to understand where to go to find what I was looking for but not really a big deal.
Time used: 1-2 years
Frequency of use: Weekly
Airbrake is one of those tools we can't live without. It gives us so much visibility on the health of our application and allows us to cache bugs before they become big issues!
Ease of use, great functionality
It can be a little expensive if you have a lot of projects, but it is absolutely worth it.
Time used: 2+ years
Frequency of use: Daily
Likelihood to recommend
Airbrake is the best error collection service we have ever used. It's simple easy and efficient. It collects and aggregates errors beautifully and makes it easy for our engineering team to triage issues based on priority. We would be dead in the water without this!
It gives track of all errors happened in your application. It helps to consolidate all errors in one place. Love the work developer put in Airbrake
Airbrake lets you know of the problems immediately when they occur, with the parameters and session; and in many cases we can fix them before customers have a chance to notify us. This gives us the ability to bring a superb service to our customers