Both them and exceptional seem to be in zombie mode. Massive bugs that have remained in place for what feels like years, no new features etc. I'd like to go with someone who cares!
That's what errbit is for. You only have to use the Airbrake libraries for reporting the errors, and errbit hosted locally collects/notifies/displays them.
If you already integrated with Airbrake, you just have to reconfigure the host it reports to, to your own errbit server and it'll swap everything over from deploy tracking to error reporting.
Errbit is an active project, https://github.com/errbit/errbit, and error reporting libraries don't tend to need a lot of maintenance.
Not sure if this surprises anyone but it surprised me when I found it - I use Google Analytics for iOS. Their library handles platform exceptions and I use it as a catch-all for ones I didn't see coming: https://developers.google.com/analytics/devguides/collection...
I also use Test Flight's reporting to do the same but I don't push that lib to production usually, where as the GA one is already handling analytics, so it ships.
Don't know which is best but we used airbrake and getexceptional in the past and it had massive issues.
We now use BugSnag on 4 rails apps (ruby and js) + one node.js app and it just works.
We stopped getting exceptions a dozen times from a few hours to a couple of days. And no the exceptions didn't came up after that delay, it's like they were never sent.
James from Bugsnag here, we're constantly rolling out tons of new features to speed up the find/fix/deploy bug hunting cycle. I'm surprised so many people are still using emails for error monitoring, using a hosted service like Bugsnag/airbrake/rollbar will massively help with productivity and actionability.
ProjectLocker (where I work) has integrated exception tracking, so I use that. Especially useful: Twitter notifications of exceptions, which show up on my phone.
For non-web, home-made exception handler that dumps the trace to syslog. Then, FATAL and ERROR-levelled entries are forwarded by email (rsyslog's ommail module; http://www.rsyslog.com/doc/ommail.html).
For web, I mostly use Django and Flask and both have [almost, in Flask's case] built-in one features, that sends an email with backtrace and request details when a bug happens.
I've been really disappointed by how little development has been put into Airbrake. It's hardly changed or improved in the all the years I've been using it. I'll look forward to checking out Rollbar.
We've been using Airbrake also, have been experiencing quite some issues with exceptions not showing up and slowness of the web ui.
I've been using Sentry [1] lately and it has been excellent.
Only issue has been that using SSL from Java was quite troublesome as their certificate is not supported by the JVM by default [2].
When your code crashes, it (usually) generates a report telling you what went wrong. This is an exception report.
An exception tracking service provides an place that you can send, store, and index these reports. It'll usually allow you to view them, search them, group similar errors, and generally provide tools that are useful when trying to resolve the problems that are occurring.
We eat our down dog food and use newrelic and logentries. We've a few big updates in the coming months. If you would like to get early access please email ben@airbrake.io
Rollbar here as well and TestFlight for iOS. We'd love to use Rollbar for iOS as well, but the support isn't great right now. That said, their support team has been great.
After using an email-based homegrown solution that I thought was sufficient, I gave RayGun.io a shot. I use it for .NET exception tracking and I am about to wire it up to a Rails app, and a very very large Backbone JS application.
It is really quite good (at least for .NET). The management UI is great and does a very nice job of grouping duplicates, similar issues, etc.
I already use some dev tools from Mindscape (their .NET ORM, LightSpeed) and their products and support are top notch in my experience.
43 comments
[ 4.3 ms ] story [ 99.2 ms ] threadIf you already integrated with Airbrake, you just have to reconfigure the host it reports to, to your own errbit server and it'll swap everything over from deploy tracking to error reporting.
Errbit is an active project, https://github.com/errbit/errbit, and error reporting libraries don't tend to need a lot of maintenance.
We use the self hosted solution. Works great!
I also use Test Flight's reporting to do the same but I don't push that lib to production usually, where as the GA one is already handling analytics, so it ships.
For web, I mostly use Django and Flask and both have [almost, in Flask's case] built-in one features, that sends an email with backtrace and request details when a bug happens.
Should I pay more attention to alternatives?
We used to use Exceptional because it was really cheap, but maintenance and bugfixes seemed to have stopped so we made the switch
I've been using Sentry [1] lately and it has been excellent. Only issue has been that using SSL from Java was quite troublesome as their certificate is not supported by the JVM by default [2].
[1] http://getsentry.com [2] https://github.com/getsentry/sentry/issues/903
Edit: Rollbar looks interesting. Too bad they don't have an API for Java.
An exception tracking service provides an place that you can send, store, and index these reports. It'll usually allow you to view them, search them, group similar errors, and generally provide tools that are useful when trying to resolve the problems that are occurring.
We eat our down dog food and use newrelic and logentries. We've a few big updates in the coming months. If you would like to get early access please email ben@airbrake.io
https://twitter.com/cjbprime/status/347467911050448896
It is really quite good (at least for .NET). The management UI is great and does a very nice job of grouping duplicates, similar issues, etc.
I already use some dev tools from Mindscape (their .NET ORM, LightSpeed) and their products and support are top notch in my experience.
http://raygun.io