#hoptoad

sad puddle (or not?)

жаба

жаба  Breviceps fuscus

Part II Step by Step guide to get hoptracker working for your app. Softwire Intro: Base app for Hoptracker which pulls errors from Hoptoad and adds them as bugs in Pivotal Tracker Project. It is still an alpha stage app with very basic user interface, no administration module yet, so all details of projects available for all, essentially for internal use as of now. Steps in softwire: 1. Goto http://softwire.sapps.in 2. Click on New app. This will ask you to provide app related details: a) name of your app b) Hoptoad app name (.hoptoadapp.com : Its the portion that softwire is interested in.) c) Hoptoad Auth Key (Get this from hoptoadapp.com) d) Pivotal Tracker Project Id e) Pivotal Tracker Auth Key (Again log into Pivotal to get this) 3. Create the app and see it listed in the listings page. Note the "Id" field of your app (as you will later use it to configure the hoptracker in your app). Bear with me at this point in time for atleast the Id should have been hashed. The next release will have a better approach to this. Thats it, you are done with the registration of your app with softwire and it is now ready to do the bug movement provided it is notified to do so. This notification happens via hoptracker plugin in your app. Lets see how that is done in a bit. Hoptracker Intro: A Rack based app to log hoptoad errors onto Pivotal Tracker. This plugin communicates with softwire (http://softwire.sapps.in) application and notifies whenever an exception occurs. Softwire, then pulls the error from Hoptoad and adds it as a bug in Pivotal Tracker. Steps in hoptracker 1. Drop the plugin in your projects' vendor/plugins folder (script/plugin install [email protected]:sapnasolutions/hoptracker.git). 2. In the environment.rb add the following line: config.middleware.use 'Hoptracker::Rack' 3. Create hoptracker.rb file in your initializers and drop in this line: Hoptracker.app_id= (This is the Id that you got as part of app creation on softwire.) 4. Restart your server and start getting your hoptoad errors onto your pivotal tracker project. Enjoy! P.S: This is still a work in progress project and does not contain an admin interface nor does it have any test cases! :( . Contributions are welcome and appreciated!

Part I Background: At Sapna, we use: 1) Pivotal Tracker for project management where all the stories/ chores and bugs go in. 2) And we use Hoptoad to notify errors in the app. The problem: Once an error comes to the mail box or we check it out at app.hoptoadapp.com, one needed to copy paste the error into Pivotal Tracker so as to track the error to completion. And this is manual job of copy/paste and sometimes, one tends to forget to the same. So we saw a need to automatically move errors from hoptoad into pivotal tracker. As of now Hoptoad support adding tickets to lighthouse projects for a price (check: hoptoadapp.com). So this got us started on Hoptracker. Initial design: We wanted to write this rack app (hoptracker) which checks the response headers to see for errors and if found: 1. Check hoptoad for latest errors 2. Check pivotal tracker for the list of hoptoad errors (we add the hoptoad error id as part of the story/bug name). Any delta that it results in. 3. We add them to Pivotal tracker. This would work fine but the problem here is that for every error, all the 3 steps would usually run and then the response would be sent to the user, which potentially will slow down the app, which is not desired. Alternate design considerations: If we moved these steps to a background process and not interfere with the response, then that would be ideal. So we planned to use delayed_job to do the background processing of the same. Then again, the plugin hoptracker will come with a dependency that every app which would use hoptracker needs to have delayed_job gem installed and the table created. A dependency like this, we did not want to inject. Moving forward, we thought it would be right to move these steps to a small app which is doing the work for all our apps, more like a Saas. Thus softwire was born. The negatives of such an approach is that, we now need to have an admin interface in softwire where apps need to be registered with the necessary (hoptoad/ pivotal tracker) details. But then we voted that this is a much cleaner approach and hence built it. How did we solve: Hoptracker: The hoptracker plugin which still is a rack app, on receipt of an error just notifies softwire of the error. Softwire: Each app as part of using the hoptracker plugin, needs to first register with softwire and provide app related (hoptoad, pivotal tracker) details. Softwire then produces a unique hash which needs to be provided to the hoptracker initializer in ones app. Please checkout the readme of hoptracker and softwire) for further details or read up part II for a step by step usage of hoptracker/softwire. Once the above process is done. Softwire maintains a local database of all the hoptoad errors already logged into pivotal tracker. Hence the second step ("Check pivotal tracker for the list of hoptoad errors (we add the hoptoad error id as part of the story/bug name). Any delta that it results in.") is avoided by looking into the local database of errors and the delta set of errors are built locally. And then the third step of insertion of new errors into pivotal tracker happens. Checkout Part II for a step by step tutorial in using hoptracker and softwire.

Late last year, Airbrake was acquired by the team at Exceptional, inc. We're extremely excited about this move and we'd like to explain why. ### A brief history We created Hoptoad in the fall of 2007 and launched it publicly in spring of 2008. We had been tracking our errors previously with an email notifier that flooded our inboxes with repeat errors, many generated by search engines requesting weird URLs. In 2011, we renamed the product Airbrake. Over the years, Airbrake handled billions of error reports for thousands of web applications from all over the world. We kept the product focused on grouping similar errors, notifying developers once per error, and displaying the backtrace and session information to help debug the issue. ### A serious commitment As the number of customers and errors increased, we spent a lot of time addressing scaling issues. There were times we'd have 150,000 requests per minute, or requests with 500MB of session data. Running Airbrake was like being under a constant DoS attack. So, we spent very little time working toward our vision of a product that integrated more completely with developer tools. Last year, we were approached by the Exceptional team and their Chief Strategic Officer, Jonathan Siegel (who has created or invested in [RightSignature](http://rightsignature.com), [RightScale](http://www.rightscale.com/), [Intercom](http://intercom.io), and [Iron.io](http://iron.io)). Exceptional had a team ready to work toward the same vision we had for Airbrake. ### The future After getting to know the Exceptional team, we felt their serious financial and team commitment had the best chance to turn our shared vision into reality. We agreed to sell Airbrake to Exceptional. The new team has been handling all support issues and feature work for several months now. We're very pleased with their work so far. We continue to provide web design and development consulting and are developing [Trajectory](http://apptrajectory.com), [Copycopter](http://copycopter.com), and [apprentice.io](http://apprentice.io) to help solve problems for web design and development teams. ### Thank you If you've been an Airbrake customer, thank you! It's been a great experience for us and you continue to be in good hands with the new team. Read more about the acquisition at [TechCrunch](http://techcrunch.com/2012/02/07/exceptional-acquires-error-tracking-application-airbrake/) and the past, present, and future of Airbrake at the [Airbrake blog](http://blog.airbrake.io/airbrake-news/how-exceptional-and-airbrake-first-met/).

via @felixge

Just a quick heads up: The Airbrake Notifier's repository is now http://github.com/airbrake/airbrake instead of being under the thoughtbot account. The URLs will still work for now because there's a fork under thoughtbot, but that will be going away in a week or two, so update your sources. Any pull requests or github issues you had on the notifier have also been moved over, so make sure you check the right project in case you think yours went missing. This won't affect anyone who's using the gem in their Gemfile, so we'd encourage you to use that instead of pulling directly from git.