We think we differ in many ways, but here's some of the current highlights:
- Airbrake & Exceptional are fairly focused on Ruby (although there are providers for other languages and platforms, often built by individuals outside those products). We wanted to make supporting other platforms a key focus and will have the app alter the display based on where the data comes from (for example, you'd have very different expectations of an iOS crash report than a rails crash report). I hope that makes sense :-) At present we have support for .NET, WinRT, PHP and have Ruby, JavaScript, Objective-C and more under development at the moment.
- We know that email notifications can be a pain. We've started life with what (we hope) is a much better approach. Email on first exception of a given type being seen, then again as thresholds change, or if recurrence is concerning. You don't get an email for every single error.
- Exceptions are a first step. We have fairly lofty goals but if we can nail a great experience for exceptions we know we'll be on the right track for other other information to help developers / operations folks.
That's just a simple run down and isn't exhaustive by any means -- we're just launching and your feedback is very much appreciated by me and the rest of the team :-)
Pricing seems to favor Sentry, depending on how one weights days vs event # history, they have a similar focus on multiple environments for error clients, many, many plugins for third party service integration, and the awesomeness that comes along with having their open source codebase.
And the one information I'm always looking for on error reporting service webpages: Is this intented for desktop applications or web applications?
We certainly need to surface more in depth information prior to needing to sign up (once logged in we have links to various provider pages but they should absolutely be public).
To help, here's some details that will get more visibly linked shortly:
http://raygun.io/raygun-providers/-net-framework-and-winrt
http://raygun.io/raygun-providers/php
It's a start but we will look at providing even more details (we need to also make the underlying API specification public so it's easier for folks to write against it themselves).
All our providers are on github here also if you're keen to poke around:
- https://github.com/MindscapeHQ
I hope that helps and thank you for reminding me to make sure that information is more easily discoverable!