cron scripts should log everything, but only send mail for errors

[Martin Pool]

I think we want all cronscripts to

 - emit to stderr (and from there through cron to mail) all messages of severity ERROR or higher
 - send everything to a log file (i guess opened directly, unless we especially want to go through syslog)

This should be pretty easy to do on top of python logging; we just need to decide what configuration options if any are needed. (Perhaps there is some standard argv->logging mapping?)

See launchpad-dev thread "cron script error output handling".

[Tom Haddon (mthaddon)]

I think the "send everything to a logfile" part is something we should just be defining in the crontab entry. Otherwise we'd have to define log file locations for every individual script and changing them would be unnecessarily complex.

[Stuart Bishop (stub)]

We recently added a cronscript.ini control file. Would it make sense to extend this?

[DEFAULT]
enabled=True
# Log INFO or higher messages
log=/srv/launchpad.net/logs/%(name)s.log
log_level=INFO

[process-mail]
# Log DEBUG3 or higher messages
log_level=DEBUG3

With the config to shortly be available over the network from a central URL, it could be easier to control that editing and pushing the crontabs.

[Stuart Bishop (stub)]

All the scripts use the same logging code so this can be fixed in one place for everything. canonical.launchpad.scripts.logger_options() sets up the python logging system and command line arguments, and everything else just uses the standard Python logging module.

[Launchpad QA Bot (lpqabot)]

Fixed in stable r11637 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/11637>.