Log messages exhaust disc space

So I'm thinking we run dblog_cron() whenever a migration starts to delete log messages based on the "row_limit" config key of the "dblog.settings" config.

-1. This would slow down the migration drastically.

The proper solution is to contribute patches to prevent those deprecation errors from being triggered in the first place, and adding them to the recommendations, i.e. to https://git.drupalcode.org/project/acquia_migrate/-/blob/recommendations....

Did 🐛 Fix deprecation error: Calling Sql::__construct() without the $migration_manager Fixed and 🐛 Fix deprecation error: Calling Migration::getMigrationDependencies() without expanding the plugin IDs Fixed help reduce this problem?

-1. Drastic slow down is exaggerated. A few SQL queries per migration import task is < 0.1% impact. Total cost / benefit -- that would save our team time tracking down logging issues across all of Drupal.

Proper solution in a perfect world is as you describe, but we're balancing other constraints.