In Go it's really easy to integrate BugSnag with the logrus library. We can then hook up Bugsnag to Pagerduty to notify our on call if there is a sudden spike in errors. Review collected by and hosted on G2.com.

The information Bugsnag captures in Go isn't that useful. Stack traces can be misleading. I'd like to track multiple levels of log in Bugsnag but not necessarily report them all through to Pagerduty (i.e. I'd like to also capture warnings but not have them ping the on call). It's very much an all or nothing tool that can only be configured at a coarse level.

Additionally the options for when it should notify aren't that useful. The option for exponential backoff on the notifications seem to be "for all time" whereas it would be more useful if it reset after a short period. If the errors settled down and we didn't see any for a week, I want a single new instance of the same error to notify me again. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

Bugsnag is very simple to set up and maintain; it has powerful search capabilities and workflow mechanisms, with lots of additions information required. It stores everything you could need to know about the bugs that it tracks and comes with an API and the abilities to export data for use on dashboards etc. Review collected by and hosted on G2.com.

The API can be a little cumbersome and the documentation isn't awesome at times. Many of the features that are on use on the site don't appear to be documented, and we had to watch the network requests to work out how to use them. Review collected by and hosted on G2.com.

I, as a developer mainly doing frontend, enjoyed the simplicity of adding tracking to our Angular app (we did it slightly differently from how it was suggested, though, we decorated the log provider to send any error level message as an error). The integrations (with Slack) are nice. Review collected by and hosted on G2.com.

Some issues that are probably on our side – we keep seeing local errors there (but not always), probably a bug in our check which environment it is, but TBH, it doesn't really bother that much because we can sort by Production or Live. Review collected by and hosted on G2.com.

- Alerts come via email when error happens and it's been quite reliable for these past year.

- This might be subjective, but the interface is really good compared to their other competitors.

- They have a really reasonable free-tier plan Review collected by and hosted on G2.com.

It would be nice if they could also monitor background jobs. Review collected by and hosted on G2.com.

Production error monitoring, automated ticket creation, understanding the impact of the bug Review collected by and hosted on G2.com.

The new UI, error grouping algorithm is not very accurate, especially for JavaScript. Review collected by and hosted on G2.com.

The ease of use, and the ability to be able to prioritize. Review collected by and hosted on G2.com.

When you reset all the bugs in order to see what is actually coming through, the old urls throw 500s. Review collected by and hosted on G2.com.

I love how reliable it is and how we can quickly debug issues in our code base. Review collected by and hosted on G2.com.

One thing that annoys us is how complex the interface is getting. It used to be simple but shortcuts keep changing and the UI is getting very cluttered with data we don't need. Another thing is that the application is getting slower overtime which makes us come back less often. Review collected by and hosted on G2.com.