From: Eric Hodel <drbrain@...7.net>
Date: 2007-03-28T05:15:12+09:00
Subject: Re: Ruby best practice re handling system exceptions/application errors/audit events?

On Mar 21, 2007, at 18:24, Greg Hauptmann wrote:

> Hi all,
>
> What is Ruby best practice re handling system exceptions/application
> errors/audit events?  (mostly for usage with Rails, but also for  
> general
> Ruby apps). How do Ruby developers normally handle the following  
> categories
> of event?:
>
> a) Uncaught exceptions (i.e. bubble up to top)
>  - Usage: System failure / developer can't do anything
>  - Approach: Let exception bubble to the top
>  - Logging: How? Rails: Ensure rails exception framework will issue
>    a "logger.error" message to the logs?
>  - Alerting: Alert (SMS/Email) based on trigger from an uncaught
>    exception.  Rails: Use of "exception_notification" plugin perhaps.

I send emails for uncaught exceptions in Rails.  It gets me to fix them.

All other exceptions I handle appropriately.

Appropriately means various things depending upon the exception.