There are no options for configuring queue worker logging. Everything just gets dumped into the single worker.log file. That file gets incredibly huge and unworkable when running a lot of queue jobs. Can there be an queue worker logging option like the other logging that I can configure to be broken into daily logs and cleaned up automatically? See: https://laravel.com/docs/5.4/errors#log-storage
Run a lot of queue jobs and watch your worker.log get out of control.
Just to clarify; the worker.log file you mention, is that the stdout_logfile in your supervisor configuration?
Do you really have to log stdout? Actual errors should still be logged to the default log and handled by the configuration rotation settings.
Yes, it is the stdout_logfile in supervisor config.
Good point - in production, I can't see a good reason to log stdout. So
sounds like my issue can be solved by simply removing the line "
stdout_logfile=/home/forge/app.com/worker.log" which will result in only
errors being logged to my default log.
Thanks :)
On Sun, May 21, 2017 at 10:07 PM, Simon Svensson notifications@github.com
wrote:
Just to clarify; the worker.log file you mention, is that the
stdout_logfile in your supervisor configuration
https://laravel.com/docs/5.4/queues#supervisor-configuration?Do you really have to log stdout? Actual errors should still be logged to
the default log and handled by the configuration rotation settings.—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/laravel/framework/issues/19299#issuecomment-303000302,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKdsMLw0yNC7Igiem-mjVE3CNBcjgAG0ks5r8RgigaJpZM4Nh4i5
.
You could run your queues in production with the -q, --quiet flag.
This disables messages in the console or in supervisord logs.