Bugsnag Reviews

Bugsnag is a useful and reliable product: you can install an additional library to your source code and email or other notification will arrive in case of exception occurs.

We can group similar bugs and compare them.

Able to show additional information to help debug with an audit trail.

After usage of Bugsnag I decided not to write my own exception catcher, Bugsnag is more flexible when doing such things.

Everything is OK: Bugsnag stays on the market for quite a long time, so it fixed all its own bugs.

The price seems to be higher than could be.

From time to time it is useful to try another rival service with the same functionality.

It allows you to achieve exactly what you expect and solve your problem. Because sometimes it is not so easy to distinguish certain exceptions among others and find a weak point in the application.

When I write a native Android application, this exception catcher helps me a lot. It saves time, money, and my nerves, allows me to fulfill the task in time.

The testing process always goes with fun. When we start to use BugSnag, our team remembered and laughed at the movie "It's a Mad, Mad, Mad, Mad World". That time when Sylvester Marcus exclaims "You bug me now!".

Bugsnag has great UI For tracking bugs. It almost always captures and displays enough information to debug an issue and not as confusing compared to other bug catching software. Pricing is also reasonable.

My only complaint is I wish emails could be customized more to show more info without having to click the link.

Read review

The problem we were trying to solve is managing our bugs and the benefits have been an all in one solution to manage our bugs.

The real time capability and ability to group similar bugs. Also ability to show additional information to help debug such as audit trail of click events.

There is nothing to dislike. This has more than enough out of the box and gives ability to add more custom information.

Definitely use this tool for error monitoring over others!

Trying to capture backend and frontend errors our users are facing.

Excellent filtering error and notification of new messages. Bugsnag simplifies the categorization errors and easily integrates with tracking and command problems sending messages.

Bugsnag is very easy to set up and maintain; It has powerful search capabilities and slotting mechanisms with lots of additional information. It holds everything you need to know about errors that it monitors, and comes with API and data export capabilities for use in dashboards, etc.

I would like to specifically note that many functions of this service are not documented well.

A strong solution for the company which developing own software and have own quality assurance engineers. It is a big bug finder and has really fast work to address them. A good platform for automated diagnostics.

We just use it for error notification. Further debugging was not really useful, thanks to Bugsnag.

For me, it is a very easy way to automatically collect diagnostics. Working well with web and mobile which really suit me so much. I can see all situation about errors by first reason. Also, I have a chance to track release health.

I don't have any bad issue with this software. But explanation about working tools should be more simple. Generally the productivity of that platform doing everything that we need.

The software is really very powerful. Will always give you the best picture of errors. So you will know from where they come and how you should solve them. I guess you will enjoy working with automatic diagnostic. I recommend it to you.

Perfect that we have a much better monitoring system for the mistake. Much easy to know the way from where errors come from. We guess it is the best solution which helps us to solve an error. Wonderful to work with the clear way and with no harm.

It's easy to setup with our laravel installation, and it's simple to find each error and drill down into the details to find what we need to fix the issues

It's difficult to dislike a tool like bugsnag, but we could probably benefit from some advanced reporting.

It's much easier to find and crush bugs, and mark them as fixed.

Bugsnag is a simple tool that does one thing well, namely capture all the of the information around exceptions in a production Ruby on Rails app. For each exception, it captures

* request that caused it

* rails stack trace

* session information, devices, browser info.

* frequency of exception

It also notices when you deploy, so that you can ignore older bugsnags after a deploy, and allows for custom fields to be reported in the bugsnag, which we use to correlate the bugsnag to particular customers.

Again - not much to dislike. Bugsnag is a simple tool that does one thing well.

There is a workflow aspect to the product that we've pretty much ignored. Instead, we fix bugsnags as they occur, so that features around managing hundreds of them aren't interesting to us.

It does what it does, doesn't cost too much, no problems. There might be other services that do this, but this one has been reliable, so we've not looked around. In 4 years or more of using it, we haven't had to contact support even once.

* proactive notification of system problems, so that we can fix them before our customers notice.

* collecting debugging information in production so that we can reproduce the problems back on our development environment

I only go in to confirm if an error is throwing a bug. Dev has set up separate areas for mobile and web. The gui is very user friendly and it's easy to get the url for the bug I'm looking at to provide to a dev.

It's very technical wording on the bugs, so not a lot of information can be gleaned by a lower level user. The site has to be customized and whatever you are tracking has to be coded to throw errors and log them here.

It allows dev to create additional bugs to log and review. You can assign bugs to be handled by teams. URLs to direct you to a specific bug can be added to tickets externally to show you the error.

The UI is great and easy to navigate. Separating out projects or products is also possible and very helpful.

Not much to offer here since Im only using it in a limited fashion.

We are solving problems of keeping our support and product teams informed through some automated messaging when one of our customers hits an error. We've been able to decrease the customer reported bugs through our support line (expensive) by catching them earlier.

Errors appear close to real-time on the dashboard. Filtering by time or error class is really simple. Spikes in errors are reported quickly.

Search functionality is really lacking. It’s hard if not impossible to do full text search for error contents.

Bugsnag allows one to dive deep into errors to find the root cause. Being able to see the stack trace and find where the errors are coming from is super helpful.