Airbrake vs. BugTracker.net

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

It is a great Bug Tracking tool when implemented and set up the correct way initially. If you find yourself in the position of having to go through and re name fields on a project level of having to do an overhaul of the user base you will find some frustrations, these are noted in the last question.

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.

• Tracking technical issues and assigning for review and completion
• Tracking final status and quality of an application or website

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

• If you edit a field you have created (Username, status, custom fields) you lose the ability to sort/filter on this field.
• It would be nice to add more custom fields on a project specific level. Currently you can only add 3
• It would be FANTASTIC if you could sort/filter on Project Specific custom fields.

Incentivized

BugTracker.net works for what we need it to do from a technology standpoint.

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 didn't choose the product or evaluate other options, but I've been satisified with it except for tracking content changes.

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

• Decreased turn around time for defect fixes.
• Smoother builder deploys
• Clearer communication from QA to Dev Team

Incentivized