Prevent normal events from logging into the laravel.og #1979
-
|
In the most recent version 10, not sure which exactly, the package now started to write down all events, like: [backup] Starting backup... Is there a way to turn writing normal events off, but still log errors, if they happen? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
This is expected behavior in v10 — the old ConsoleOutput singleton got replaced by a backupLogger() helper that routes progress messages through Laravel's logger instead of just printing them, which is why they now show up in laravel.log. There's a log_channel option in config/backup.php for this. It's a blunt switch on its own (default channel / custom channel / false to disable entirely), but if you point it at a custom channel with its minimum level set to error, the routine info-level progress messages get filtered out while actual failures still get logged: // config/logging.php // config/backup.php |
Beta Was this translation helpful? Give feedback.
This is expected behavior in v10 — the old ConsoleOutput singleton got replaced by a backupLogger() helper that routes progress messages through Laravel's logger instead of just printing them, which is why they now show up in laravel.log.
There's a log_channel option in config/backup.php for this. It's a blunt switch on its own (default channel / custom channel / false to disable entirely), but if you point it at a custom channel with its minimum level set to error, the routine info-level progress messages get filtered out while actual failures still get logged:
// config/logging.php