If queue or database is unavailable, emergency logging should be used

[joostdebruijn]

When using this log channel with queueing and the queue is unavailable (e.g. Redis is not running or the database is unavailable), I would expect that errors occuring at that moment will be logged to the emergency channel. However, I don't see those errors logged anywhere. Maybe it's a configuration thing, however - in that case it would be nice to add something about it in the documentation.

[danielme85]

Sorry for the late response here, busy with work and house and life and all that!

That's actually a very good point, I think I just got used to doing the whole stack log channel with db+daily so I could always fall back to a log file. However, that means that I would double store all logging.

I'll take a look at this, need to make sure this thing still works on the newest Laravel updates anyways ;)

Thank you for the feedback, much appreciated!

[danielme85]

Hi @joostdebruijn,
I'm working on adding a Monolog Logger that basically just adds the log event + exception info to PHP's native error_log if writing to DB fails. This would require a working error_log setting in PHP (obviously), but other than that it should be pretty straightforward.

https://github.com/danielme85/laravel-log-to-db/blob/v3.1/src/LogToDbCustomLoggingHandler.php

Need to test this in practice, make sure we don't get any of those magical/wonderful infinite loops 👍

[danielme85]

This is now added in v3.0.2, thank you for the suggestion!