Sentry-like approach is the best approach of catching errors in applications deployed in production. It logs all uncaught exceptions - including stacktraces, and the context - e.g. user affected, request parameters, and anything of relevance. It aggregates all errors and provides stats on them. This allows us to know how often a particular problem occurs, and are able to identify and fix problems before a customer contacts our support. And if a problem is reported to us by a customer, we can easily filter errors by user, and see everything they had problems with. No more log grepping - which takes much more time, and provides less information. For some customers, we didn't aggregate app logs at all because Sentry was everything that we needed.

Sentry.io is more affordable than Bugsnag. All Sentry plans include features that are restricted to higher plans in Bugsnag.

It's an amazingly powerful tool which we use in our firm for error reporting, monitoring, and resolving by checking the stack trace it provides line by line. Best part I like about Bugsnag is its ability to share the stack trace for the error which helps me figure out the problem better. I could integrate it easily into the internal chat tool we use in our firm, which helps me to keep notified about new error every time. The application UI is pretty simple to use and get started with, along with the filters which are really helpful.

Nothing which I can say so far. I love the whole concept of it :)

While Bugsnag is easy to setup and begin using, with the project I use and am familiar with, I personally prefer using Cloudwatch to capture exceptions and notify of these issues. My team uses both.

Bugsnag is pretty easy to use in the basic capacity of catching exceptions and notifying you of it. Viewing the stack trace, and number of instances of a given exception can be very useful

Its basic use will confuse a lot of new developers. Something about the basic dashboard and timeline seems to be misleading. I'm sure a lot of this can be overcome by customizations though.

Overall excellent app for bugs/event tracking with various integrations and super simple to integrate , works like a charm.

- real time error capturing along with entire request, headers and platform details is probably best feature of app. - works with almost all the language and frameworks. - various integrations like slack , email is very useful

- I have faced little difficulty using it with golang, as it does not append request body - only limited no users for the free accounts.

Overall Bugsnag is SUPER useful!

I've integrated Bugsnag in ALL of my projects. It's super easy to use and the setup is very minimal. If you're an app developer you should definitely be keeping track of your bugs! We've integrated Bugsnag with Slack and PagerDuty so we always know when a bug comes in. We've also used it to debug issues in production by logging certain data into Bugsnag. You could also record bugs for different app stages (local, staging, production).

The stacktrace doesn't always give you the full trace, so it can be difficult to find exactly where the bug is coming from.