Airbrake

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.

• Quickly reporting all errors
• Tracing them to the commit

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

Datadog, OpsGenie and Grafana

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

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

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

Sentry

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

• Custom Aggregation
• Multiple Applications
• Notifications

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

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.

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

• 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

Sentry

DigitalOcean, RubyGems.org, Microsoft Visual Studio Code

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.

• Tracking errors
• Early notifications about possible problems

Jira Software, Slack