Close and Go BackBack to Viget

Hoptoad: in Brief

Tony Pitale
Tony Pitale, Web Developer, July 30, 2008 4

I was notified on Monday (or thereabouts) that Hoptoad had launched. Hoptoad is a service which stands to act as an intermediary between your Rails application exceptions and your email inbox. Any notification of exceptions raised will be delivered to Hoptoad and any repeat exceptions will be combined and counted. An email notification is still sent, but more intelligently (instead of hundreds of emails flooding your inbox).

Having completed registration, I added a number of separate projects. Instructions for setting up a Rails application follows. WIth a simple plugin, and a new initializer, my Rails application was all set to go.  I was able to configure and run the Hoptoad rake test in less than a minute. I did have to update an older project to Rails 2.1 and I’m not sure which versions specifically are compatible. All other projects worked without so much as a hiccup. As would be expected, a handy feed is provided.

After receiving an exception, Hoptoad will list it on the project’s page with a handy count of duplicate exceptions:

image

Exceptions appear to be compiled by an interesting combination of exception type, controller/action, and the exception message raised. The summary page details the time for the latest of each of the exceptions. Exceptions that have been reviewed on the site are marked as “resolved” and can be hidden. I was able to cull this information using the included rake test task, modified to raise a variety of exceptions, from different actions. I ran the modified task many times over to see how the errors would be combined. Any further insight into this process would be interesting to hear, so please leave comments.

Clicking on the exception will bring up all the wonderful details including details about the environment and the backtrace:

image

For new exceptions an email notification is sent:

image

I can’t vouch for the other members of the team here at Viget Labs but, for me, Hoptoad seems like a great fit. I always felt that email, while relatively immediate, was far too difficult to wade through with a large volume (my inbox doesn’t scale). I can understand the reason for reporting every single exception though the process always seemed inelegant. Hoptoad has successfully solved this problem, given my domain. I’ll report again after using Hoptoad in production for longer than a week.

Dan Croak said on 08/04 at 09:34 AM

Hey Tony, nice writeup. Hoptoad works with all versions of Rails after 2.0, and thoughtbot will continue to support those versions.

Tony Pitale said on 08/04 at 09:43 AM

Thanks Dan! That’s great info to have.

Tammer Saleh said on 08/04 at 11:23 AM

Hey Tony,

bq. I ran the modified task many times over to see how the errors would be combined. Any further insight into this process would be interesting to hear, so please leave comments.

Right now exceptions are considered duplicates if they have the same project, exception class, file path, line number, action, controller, and rails_env.  Of course, that may all be tweaked later.

Thanks for the writeup!  We’re really excited to see Hoptoad getting so much press.

Tony Pitale said on 08/04 at 11:37 AM

Thanks Tammer for another excellent insight!

Name:

Email:

URL:

Not a robot? Prove it by entering the word below.


Remember my personal information

Notify me of follow-up comments?

We're the Developers

at Viget Labs. We write about web development trends, tips, best practices, industry events, and our projects — all with an emphasis on Ruby on Rails.

Recent Comments

Tony,

I understand and agree that the back-end shouldn’t output code (html code), and only content. The templates (aka views) should do the trick, but instead of having lot’s of if/else conditionals inside the view, you may just output the following content.

No information available

The template would loop in an array and put all the <li>’s inside the <ul>.
I don’t see anything wrong, nor...