Its been a little over a week since we officially launched Hoptoad, our centralized error catching application. The feedback we’ve received has been overwhelmingly positive, and we’ve caught about 45,000 non-test errors from 115 applications. If you haven’t given Hoptoad a try yet, come on in, the water’s fine.
Yesterday we deployed several improvements:
One of the more noticeable changes we’ve made is that the default error listing now excludes errors that you’ve marked as resolved.
In Hoptoad, you can mark an error that your application has thrown as “resolved”. Hoptoad detects similar errors, and only notifies you about the first error when it occurs. Until now, the primary benefit to marking an error as resolved was that if an error you thought was resolved occurs again, we’d specifically notify you about it again. Previously, we defaulted the main error listing to show you all errors regardless of their resolved state, and you had to click “Hide Resolved Errors” in order to remove the errors from the listing.
We originally made this design decision in order to err on the side of more visibility into all of the errors that were occurring in your application. But, based on user feedback, and a change of heart internally, we’ve reversed this so that resolved errors are now excluded from the listing, and you click “Show Resolved Errors” to view them.
We’ve also added a simple visual cue for resolved errors in the listing.
This release also includes documentation on the Hoptoad API, and the server side changes necessary to get it going. The API is RESTful, so you can use Active Resource, or use it directly if you want. We’ve also provided basic documentation on how to submit errors directly to Hoptoad without using the Rails plugin we provide – so the door is now officially open for you to create your own clients for Hoptoad – maybe Merb, or .Net strikes your fancy. For complete details on the API, check out the documentation.
We’ve also included a few other refinements and bug fixes as well, you can take a look at the changes in our lighthouse to see the full list.
Finally, thanks to Tony Pitale for his writeup on hoptoad.
We’ve got some more improvements in the works, stay tuned.