DB logs should have a max-age setting to prevent bloating table size

[timkelty]

Description

File-based logs have rotation, but with the move to db logs, we should have a way to automatically limit the size of that table.

The idea is to add a maxLogAge:

• use as a default to feed-me/logs/clear
• if set, clear on craft's garbage collection

#1487 (comment)

[frank-laemmer]

feedme_logs are often the cause for blown up databases supporting Craft CMS clients (we provide web hosting), usually the biggest table. Customer are often unaware. So plus one for this feature.

[ul8]

👍 I just manually freed up 10GB in a database by clearing the logs. Would really appreciate an automated option.

[mnlmaier]

+1-ing this, came up in one of our projects as well (though not in the realms of 10GB+, that's wild).

Also I was thinking, why should the logs be saved into the database at all, when there is an established structure with log files being stored in storage/logs (as it also is the case in other frameworks, like Laravel)? I'd prefer using the traditional approach, but maybe that's just me. if there is a good reason for storing logs in the database, I'm genuinely curious to learn more about it.

(Edit: I'm now aware that this is configurable, might be interesting to some: https://github.com/craftcms/feed-me/blob/5.9.0/README.md#customizing-logs)