in reply to Re: Proposal for Uber Error Handling Architecture
in thread Proposal for Uber Error Handling Architecture

Thanks everyone for their replies. I hadn't heard of Log::Log4perl before, and it looks like an excellent solution...a very near match to what I had envisioned. It looks like I may need to handle returning errors to the user's browser seperately, but that may be a Good Thing anyway.

I'm also now considering just logging everything to STDERR now for performance and consistency, and possibly running a cron job at off-peak hours to parse the logs for anything I might want to stuff in a database for easier review and handling.

-mark

  • Comment on Re: Re: Proposal for Uber Error Handling Architecture

Replies are listed 'Best First'.
Re: Re: Re: Proposal for Uber Error Handling Architecture
by perrin (Chancellor) on Mar 25, 2003 at 22:53 UTC
    I've done it that way before. I cron a little script that checks the error_log for anything interesting and mails it to me. "Interesting" is defined with simple regexes. This works well and keeps you from getting lots of little e-mails when something goes wrong.