TrustRadius: an HG Insights company

Airbrake

Score8 out of 10

18 Reviews and Ratings

Get a Demo

What is Airbrake?

Airbrake, now from LogicMonitor (acquired February 2021) is an error monitoring and performance insight tool. Airbrak offers real-time error alerts, rich contextual data about why errors are occurring, integration into an existing workflow, and application performance insights to enable users to identify, diagnose, and fix problems - before users get annoyed.

Categories & Use Cases

Media

Screenshot of Airbrake Account Dashboard
Screenshot of Deploys Dashboard
Screenshot of Performance Dashboard
Screenshot of Trends Tab
Screenshot of Breadcrumbs feature

1 / 5

Screenshot of Airbrake Account Dashboard

Reviews

What users are saying about Airbrake.
View all reviews

Easy to Quickly Identify and Track Down Bugs

Incentivized
Tyler McWilliamView profile
Software Engineer in Product Management at Workforce.com (51-200 employees employees)

Use Cases and Deployment Scope

We use Airbrake to actively monitor every end user's experience with our products. All of our services are monitored by Airbrake and it is the first place we check when something goes wrong. It has also helped detect several issues that went unreported.

Pros

  • Reports errors that aren't being reported to us
  • Helps to quickly identify which specific line of code is causing issues
  • Prioritizes issues by identifying which server created them

Cons

  • We use Airbrake in conjunction with OpsGenie, but I feel like there could be more room for integration between the two.
  • I think it would also be nice if there was a GitHub integration that would comment on recently merged error-prone PRs, currently, we need to dig into the error to find the commit.
  • Generally, more integrations would be nice as people often forget about Airbrake when they are stressed out about an issue.

Most Important Features

  • Quickly reporting all errors
  • Tracing them to the commit

Return on Investment

  • We are able to quickly reduce the scale of impact when bugs happen. This is the main value.

Alternatives Considered

Datadog, OpsGenie and Grafana

An excellent ally in debugging sessions

Incentivized
Daniele DolciView profile
Full-stack Developer in Information Technology at Monforte Srl (11-50 employees employees)

Use Cases and Deployment Scope

We use Airbrake to monitor problems on our frontend application. All the problems that escape the tests or the devices not taken into consideration.

Pros

  • Identify problems on devices we cannot test on
  • Give an overview of the most frequent problems
  • Report any information necessary for resolution

Cons

  • Some installation difficulties on particular less known frameworks

Most Important Features

  • List of problems with occurrence count
  • Stacktrace directly in the problem notification
  • Dashboard with summary of the situation

Return on Investment

  • It allowed us to solve PWA access problems that are difficult to replicate in tests

Alternatives Considered

Sentry

Other Software Used

Hotjar, Google Tag Manager, Zendesk Chat (formerly Zopim)

Airbrake the Bug Smasher

Incentivized
Wesley Sprague
Software Engineer in Engineering at TuneCore (201-500 employees employees)

Pros

  • Logs Errors
  • Provides backtraces
  • Custom Aggregations of Airbrake Messages
  • User Friendly

Cons

  • Search Functionality could be improved
  • Environment Param should be a drop down rather than a manually typed search field

Most Important Features

  • Custom Aggregation
  • Multiple Applications
  • Notifications

Return on Investment

  • Increased Ability to Identify Errors
  • Support for gathering more information on bugs and issues
  • Post Deployment Confidence

Airbrake helps us stay ahead of problems

Incentivized
Verified User
Manager in Engineering (11-50 employees employees)

Use Cases and Deployment Scope

When I started work in the team here we didn’t have any frontend error alerting whatsoever, and all the backend alerts were based on filtered log analysis. This was fairly hard to work with, and I was sure we were missing a lot of errors. I pushed for, and then implemented, Airbrake on frontend and then backend and the benefits were large and immediate. We found hundreds of thousands of frontend errors were occurring, and the bulk of them were simple things to fix once we were aware. We also got more timely alerts about backend problems, helping us take a more proactive approach to fixing the system.

Pros

  • Frontend error alerting and analysis
  • Backend error alerting
  • Recording and prioritisation of errors based on frequency
  • Integration with deployment pipelines to check for errors in a new release

Cons

  • I would *love* (and pay more!) if Airbrake also provided an integrated log collection service that was aligned with the error reporting
  • It can be awkward to distinguish between errors in our frontend application and in browser plugins being run by users
  • Given how wide the aggregate view Airbrake themselves have, perhaps they could identify and suggest best-practice solutions to common errors?
  • Browser errors in different user locales show up separately in different languages, even though they are really the same error

Most Important Features

  • Works with a wide variety of languages
  • Both frontend and backend
  • Simple to install and integrate
  • Reliable and comprehensive once installed

Return on Investment

  • Hugely reduced frontend errors in devices we don’t often test: means more conversions and sales
  • Lets us know immediately when there is an error: shorter error durations also means higher sales
  • Ultimately once we’ve solved all the most common bugs: more time for developers to focus on other things

Alternatives Considered

Sentry

Other Software Used

DigitalOcean, RubyGems.org, Microsoft Visual Studio Code

Reporting Errors Is Good, Airbrake Makes It Even Better.

Incentivized
Verified User
Engineer in Engineering (11-50 employees employees)

Use Cases and Deployment Scope

We use Airbrake to track multiple things: the errors that appear in the console of the end-users, to make sure that our product works as intended and to get notified about any error before the user reaches out to our Customer Care team (and get more information about the error) track the failed API calls that we have sent from our frontend. We use this to check faulty implementations or how the user is misusing our software so we can foolproof it better :D we made it kinda a habit to keep an eye on those numbers, we don't strive to get it to 0 but for stability.

Pros

  • Report errors
  • Versioning

Cons

  • Aggregated errors are not so clear why they got grouped together
  • Not clear why some filters don't work

Most Important Features

  • Tracking errors
  • Early notifications about possible problems

Other Software Used

Jira Software, Slack

Related Products

Products similar to Airbrake that may also meet your needs.
All comparisons
Sentry
CompareLearn more
BugSnag
CompareLearn more
Raygun
CompareLearn more