I don't think it is proper to have a log file to grow and grow to massive sizes when not needed. So I like to see a on/off selection for activity logging.
I don't think it is proper to have a log file to grow and grow to massive sizes when not needed. So I like to see a on/off selection for activity logging.
The MT activity log would typically need to have over 15k entries in it to exceed 2MB of storage. That's hardly massive. Being able to turn it off might give a performance boost, and thus be a good idea, but saying it is "massive" is incorrect unless you have plugins which are dumping hundreds of entries into it every day.
Mike, perhaps there is more to this matter of Activity Log maintenance than meets the eye. I've recently taken over technical administration of an MT-based blog that's been running for several years. The Activity Log, which hasn't been cleared since 2007, now has over 176,000 entries in it, is over 33 megabytes in size (by far the largest table in the MT database) and consumes 60% of the storage devoted to the site's database. One side effect of this is that I'm having difficulty dumping mt_log to save its contents for historical purposes before clearing it.
The only maintenance option on the Activity Log page appears to be the "Clear Activity Log" button. If there isn't such a capability already (in a place where I haven't seen it yet), it would be very useful to have a "log rotation" capability that would, on a scheduled basis, dump and clear the Activity Log to keep its size within manageable limits. That's something that is routine for other systems that produce regular activity logs, like the Apache web server, the MySQL database system, and so forth. Can that be added to MT?
Are there others who feel the need for taking control of the MT Activity Log?