I played a bit with generating some useful reports but I figured I should
get a better idea of what needs to be in the reports before I write them.
My idea is to have a 'report' command that takes a list and zero, one or
two dates (to limit the time span of the report, zero meaning 'everything
since the last zero-date report'). A report gives information on requests
made (zubscribe, he1p, etc., like logsummary.pl), list traffic (like Dave's
logmail) and outstanding tokens.
I suppose the global report would give info on the global requests, plus
summary info for each list (counts per request, number of messages per
list, etc.).
I'm less sure about the per-list report. I intend for it to be able to
(optionally) replace the little messages that the owner gets when someone
joins/leaves. Here's what information gets logged (per request):
list
request
requesting user - the user who sent the mail/made the request
victim - the address that the request acted on
command line - includes the modes and such
interface - shell, email, web, etc.
status - succeed, fail, stall for confirmation
passworded - was a password used
time - when it happened
What should be reported? I don't really want to have a multitude of
reports; just the two where you can optionally choose not to hear about
traffic or tokens or requests. The owner chooses what requests they care
about by setting the inform variable.
Also, does anyone know of a good table formatter? Right now I'm using
Data::ShowTable which is somewhat suboptimal.
- J<
|
|
