maybe stats data could be appended raw to files thru syslog?
put the burden of summarizing on the reporting programs.
have summarized and raw data in the same format so reports work
on both. a nightly job might condense the day's stats into
summaries to save space.
------------------------------------------------------------------------------
> Currently there's nothing to capture usage stats, but when Mj gets
> modularized to make it easier to add customization modules, I'd thought
> about an add-in to do that. The problem is that it's no insignificant
> amount of overhead to do the stats file locking, etc. for each posting.
> It would be pretty useless unless a list owner were able to retrieve
> the stats via e-mail (using a password, of course) and maybe a retrieve
> and reset. Then there's the details of exactly what stats need to
> be captured: number of messages, of course, but what else? Some
> possibilities off the top of my head:
> Counts of:
> - messages
> - message (body) sizes, i.e. bytes distributed
> - administrivia bounces
> - taboo header, etc. rejects
> - max size bounces
> - errors returned by MTA
> Also a time stamp when last retrieved and when last reset. Probably also
> when last updated. Another question is how configurable this should be?
> I'd say just enable/disable per list. I see no reason to configure each
> stat type, that's more appropriate for the report generator program that
> uses the stats.
> Comments? Please direct followups to Majordomo-workers.
|
|
