Zope has good logfiles. If there's a real error which results in a traceback, even the traceback ends up in the logfile. The conclusion is that a log message can spread over multiple lines. That's why zope's logfile entries are separated by ------.
For monitoring your logfiles, logcheck is a good solution, even though it looks a bit debian-specific at the moment. I could not, however, get it to handle the multi-line zope logfiles in a handy manner. Solution: I build my own logchecker. I had a logfile-parsing utility ("logsplitter") lying around from when I needed to make sense of three months of logfiles from a big customer at zest.
At The Health Agency we're really upgrading and improving our back end systems (buildbot, release scripts, pypi egg proxy, couple of buildout recipes) and automated zope logchecking is another step we want to take. So I cleaned up ye olde logsplitter, added logchecking functionality and packaged it all up as tha.logcheck.
Installing tha.logchecker installs two programs:
logchecker -h and logsplitter -h give you usage information.
My name is Reinout van Rees and I work a lot with Python (programming language) and Django (website framework). I live in The Netherlands and I'm happily married to Annie van Rees-Kooiman.
Most of my website content is in my weblog. You can keep up to date by subscribing to the automatic feeds (for instance with Google reader):