Live data from Hacker News

Airbrake acquired by Exceptional

blog.airbrake.io

11–20 of 33 posts

Re: Airbrake acquired by Exceptional

#11
Not being aware of Airbrake prior, I assumed it was a service for transcoding media (i.e. Handbrake in the 'cloud'). Upon learning its actual purpose, it seems like the project is yet-another-candidate for cloning in an open source project so people can it run on their own.

As a hobbyist looking to learn more, I have been making a list of services that I could clone the functionality of, in an open source project, to achieve that end. This looks like a good opportunity.

Re: Airbrake acquired by Exceptional

#14
post #9

Whoa! The cheapest Airbrake account costs $79! Are there alternatives to Airbrak & Exceptional?

Weird... it was $5/mo when we signed up less than a year ago. Seems that our price hasn't changed. That said, we're moving away from it.

Why? Well, it's practically useless outside of Ruby. The UX assumes Rack/Rails-isms, so the experience is weird for Javascript errors. Beyond that, stack traces aren't good enough to debug many issues; you need logging integration. This is especially true for minified javascript.

Re: Airbrake acquired by Exceptional

#15
Sounds like it might be time for me to roll a service like this. I used to use Exceptional, but their free plan went away, and I switched to just using exception_notifier to send emails straight to me instead. It's a useful service, but the price point just doesn't work for hobby/small projects.

Re: Airbrake acquired by Exceptional

#16
post #8

lately they've just raised the airbrake prices to more than 600% WITHOUT ANY NOTICE! I see that exceptional cost 9 usd/month (per project or account? it's not clear) I'll see what they'll do, and eventually migrate to an open alternative. 5 usd/month for 4 projects is great, 35 usd/month it isn't (speaking for a bootstrapping startup where every cent can make the difference)

Hi this is Ben. I run all things product. I take full responsibility for outages and our pricing change and I'd like to share what we're thinking--and I'm happy to have constructive feedback.

We have regular usage of 3000+ requests per second between our products. We have 12+ languages/frameworks that feed us exceptions. We also have integrations with PaaS providers like Heroku, EngineYard, AppFog and others. We also get hundreds of support requests each week. Part of our mission for embracing both of these products is to complete a vision that includes many powerful additions. But to get there we knew we needed to both retool the architecture for scale. We also wanted to keep under 24 hour turnaround time for our support.

When you look at our historical pricing there is no way we could meet our expectations of providing high reliability to our customers, a high quality of support and maintain all the bits that feed into the product--not to mention our vision for the future.

We tested our pricing changes with over a hundred of our users and they adamantly agreed--charge us more--make it rock solid--and let's see some of those features (e.g. search!).

And in general--our philosophy with pricing is this: we are developers. All of our customers are developers. But within this group there is a distinction--the side-project developer and the corporate developer. You are probably a corporate developer when you've advanced to having a company credit card. To you, our pricing is trivial for a production infrastructure service (see AWS or even Salesforce and friends). For the side-project developer--we are never going to be inexpensive enough. And we don't want to break your back to get great service from us! In fact, if anyone has been adversely affected by our plans, you should tell me! I take responsibility and want to hear from you.

I'm ben@airbrake.io or just give me a call at 415 500 5207. Although I'm in Berlin right now with some of our awesome users http://instagr.am/p/GtrfVDlnsy/, so if my speech is slurred or I'm slow to respond this evening, you know why. :-)

Re: Airbrake acquired by Exceptional

#17
post #13

Is anyone else getting confused too? who did acquired who? On http://contrast.ie/ is stated Exceptional is acquired by Airbrake.io (Hoptoad). And here is state the opposite... will Exceptional continue to exist or Airbrake? Or Both?

I believe Exceptional was acquired by Jon Siegel, and then Exceptional, under its new ownership, acquired Airbrake. I haven't seen anything that indicates which brand will take precedence or if both will continue running.

Re: Airbrake acquired by Exceptional

#18
post #10

Is there a reason to use any of these services given how trivial it is to set up an open source alternative? You can push errbit to heroku in 5 minutes and you're done. Perhaps there is a level of service here and a business I don't see, and I'm a huge heroku and third party service user, but I don't see the need for a monthly service fee to aggregate and send exception notifications. It's either a self deploy or a f…

Having used Airbrake (when it was Hoptoad), Exceptional, email notifiers, NewRelic, and "rolling your own", I would say that there is definitely value in having a service to handle this for you.

Rolling your own is more effort than it's worth. On top of that, exception tracking is not something you want to have to worry about when your world comes crashing down, and that's exactly when a hand-rolled solution is most likely to fail. (i.e. Are you running your hand-rolled tracker in the same Heroku instance as your app? Then how do you know what went wrong when your app comes down? Are you running it as a separate Heroku instance? Why are you wasting money/resources running twice as many instances as you need?)

NewRelic is nice in the way that it integrates with other charting/reporting for your app. However, on a day-to-day basis, too many errors/exceptions are not caught by NewRelic making it ultimately unreliable. Also, you don't get nearly enough context with error reports to be able to debug the root cause (though they have been improving in this regard).

Email fails as a solution the first time you accidentally deploy an error that gets hit 500 times a second. This is especially true if your app, itself, needs to send emails. I've witnessed a situation where exception email notifications have caused message rate-limiting to kick in preventing customer targeted emails from being sent. Now you have two problems!

I won't say that Airbrake or Exceptional are perfect, but they are good for what they do. Obviously every situation is different, and you have to weigh the pros and cons (e.g. How much traffic are you receiving? Do you have a dedicated Ops team that can handle deploying/maintaining a hand-rolled solution? How much revenue are you loosing because of exceptions? Is your app targeting individuals that are likely to be turned off the first time they see a 500 page? or can you afford to have uncaught exceptions for now?). By no means, though, would I dismiss these solutions out of hand.

Post reply on HN