Manager log limit

OK this is really minor, but I’d still like to see it...

The "Number of log entries" setting in the MODx manager just prepopulates the "No. of results" field in Reports -> Manager Actions (also known as the "Audit Trail"). What I’d really like is a way to limit the number of entries in the modx_manager_log table (so if I set it to 100, only the last 100 actions would be in there). Otherwise that table just grows and grows, which can slow down backups with data that I pretty much never need.

Alternatively (or additionally), a "Clear Manager Log" button might be useful.

You can kinda/sorta do this by clicking on the link of the manager table in the Backup Manager. Same with system events. Though with large DBs you run into issues maybe there too.

I concur and this would make for a great Jira request, especially if accompanied by some code to make it work.

I vote for the log limit. And while we are at it, I see the "System Events" sometimes add megs of data to the db and never get noticed until something starting to break or u see your webspace meter going up like crazy.

There is a link to clear the manager log buried in the text after you’ve done a search, but it’s kind of hard to see and easy to miss.

Perhaps if there are events in the event log, that should come up in the Welcome page of the Manager?

What event would you tie the "clean database" event to? If you add it to a front end event it will add overhead, in the backend it will depend on a manager event. Seems to me like a server script triggered by a cron would be the best solution and it could be triggered to do other things like optimize the database and maybe even do a backup.