Exception Notification Emails

Rick's Avatar


13 Jun, 2007 02:53 PM

I've been noticing a trend with the emails people are sending to Lighthouse. Folks have been directing exception emails from their web applications to Lighthouse. The problem with this is that the vast majority of these are duplicates. There are many instances of the same exception with slightly different parameters. I just don't think each of these deserves a ticket of its own. Here's a possible solution: send these to your own email box, and manually forward valid bugs to Lighthouse.

What do we do with exceptions? I wrote a clone of the popular exception_notification rails plugin called exception_logger. This stores exceptions in the database a provides a simple interface to browse through them.

I'd like to come up with a good solution for everyone. For now, I'll have to ask folks to quit sending all of their exceptions to Lighthouse. If you have ideas or problems, let me know!

  1. 1 Posted by Joe Van Dyk on 03 Aug, 2007 10:24 PM

    Joe Van Dyk's Avatar

    Why is it a problem? Too many emails?

  2. 2 Posted by Rick on 25 Aug, 2007 04:40 AM

    Rick's Avatar

    I think those records need to live in some more temporary location before they get assigned as tickets. On the other hand, part of me wonders why Lighthouse can't be that 'temporary location'?

    We're working on a bulk editing interface, but I still would rather not have folks spamming Lighthouse like that.

    I have some ideas of adding on to beast to make a more general customer support tool and using that as a front end to Lighthouse. Depending on how that works out, we may somehow add it into Lighthouse. I don't know, I have this notion that it should stay focused.

Discussions are closed to public comments.
If you need help with Lighthouse please start a new discussion.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac