Skip to content
Discussion options

You must be logged in to vote

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

'backup' => [
    'driver' => 'single',
    'path' => storage_path('logs/backup.log'),
    'level' => 'err…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by zokistale
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants