Airbrake vs. FogBugz

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

FogBugz has been a very useful tool to our organization, and much preferred over other options we reviewed, mainly JIRA. There are still some improvements needed, but with the fairly recent acquisition by DevFactory, we have a great deal of hope for what is in store given DevFactory's focus and transparency. It seems like both DevFactory and FogBugz customers are eager for substantial improvements on the front-end, but there is/was a great deal of backend housecleaning that definitely needed to take place first.

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.

• Tasks, Subtasks, and notes. All three of these areas were critical for our team. Tasks in Fogbugz were a bit easier to see than in more bug based software like Trello or JIRA
• The entire screen is used to view a task or case. Clicking on a task or case will open up and take up the entire screen, aside from the sidebar nav columns. I like to see details and I think Fogbugz does this very well, using up as much digital real estate as possible.
• Flowcharting in Fogbugz with Creately is nice - instead of getting an exterior flowchart software like Lucidchart, Creately works right in Fogbugz.

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

• The simplicity of a single admin type user is not great because anyone who can create a job or client in the system, can also add and delete users. Content and User administrative rights should be separated.
• There are ways to change the terminology/lexicon within the tool, but we are not able to get it to work even after reaching out to tech support. So we are forced to use the system terminology that doesn't match up to our company making training a bit difficult.
• There is a subscribe function that you can opt into, there should be a way to add subscribers as you create a new task.

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 like JIRA a lot better than Fogbugz for many reasons. If I had a choice, I'd use JIRA every time

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

• Saves time by quickly allowing Developers to make the necessary notes without getting bogged down in bloated UIs
• Has allowed us to look back easily and see the exact code changes made for the exact Case to aid in decisions for current changes, increasing the certainty of the decided path, without regression

Incentivized