Airbrake vs. Omnissa Intelligence

Airbrake is very good at what it does, I don’t really have any criticism at all on that front. It’s less well-suited when bugfixing goes beyond the immediate error and means looking at a lot of context (particularly asynchronous context) like logs.

Incentivized

Crittercism is definitely, in my opinion, best for software testers/engineers. We are the faces behind proper app behavior. However, I'm sure there are other scenarios that would benefit from this program. Engineers should should use it prior to sending out builds to see if anything major is crashing or going wrong behind the scenes to diagnose the problem before going into testing/production

Incentivized

• Integration with most of languages and frameworks as well support via existing logging configs.
• Aggregations on occurrences which helps to understand and analyse issues better.
• Web UI displays all error related parameters which I never could have figured out in manual debugging.

• Identifying crashes users are experiencing.
• Allowing us to see how many times the crash occurred.
• Allowing us to see what times the crashes have occurred.

Incentivized

• We use Airbrake in conjunction with OpsGenie, but I feel like there could be more room for integration between the two.
• I think it would also be nice if there was a GitHub integration that would comment on recently merged error-prone PRs, currently, we need to dig into the error to find the commit.
• Generally, more integrations would be nice as people often forget about Airbrake when they are stressed out about an issue.

Incentivized

• Pointing to exact line number of the crash
• A more explicit navigation bar (a little confusing for the user)
• Third-party API specific crash reporting (instead of just listing the endpoint)

Incentivized

I love to use Airbrake and New Relic in conjunction. New Relic has better metrics and data that you can really dig into (especially for optimizations), but the error part has always been kinda meh. I fee like Airbrake has done an awesome job at this

I use both for different purposes. Twitter Fabric integration was easier for setup purposes and documentation was a lot clearer than Crittercism and geared towards Swift more so than Objective-C. Twitter Fabric is also better with real-time emails pointing to exact line number for a bug. Crittercism is better for bread crumb trails and stack traces to see the user flow and how a problem ending up becoming a problem in the first place.

Incentivized

• Hugely reduced frontend errors in devices we don’t often test: means more conversions and sales
• Lets us know immediately when there is an error: shorter error durations also means higher sales
• Ultimately once we’ve solved all the most common bugs: more time for developers to focus on other things

Incentivized

• Allow us to release iOS versions quicker to the app store
• Help us solve bugs and view bread crumb trails on money-making actions within the API
• Points us to problems in the stack trace with a direct correlation to our route creation aspect in the app

Incentivized