Jordi Boggiano

You can add `var_dump(class_exists('Psr\Log\LoggerInterface'), (new \ReflectionClass('Psr\Log\LoggerInterface'))->getFileName());` above your `new YamlExpander` line, hopefully that will show you where it came from at least.

I think maybe what we could try here is to close the stream when `reset()` is called, as that should be called between jobs in long running processes. That should...

Normally formatting happens after processing, so this should never be a problem. Have you experienced an actual issue?

Right, exactly my thinking @stof - sounds to me like these processors should all record stuff in extra as they are meant to, and then the final formatter can use...

Yes it should work.. Have you tried? :)

If you're using Monolog 3, you can call $logger->close() as well as $logger->reset() in between "jobs" or whatever you have as a good point to do this where it makes...

You can also close the UDP handler directly of course, if that's more appropriate, but IMO closing/resetting everything between jobs in long running worker processes is a good approach.

1. Use a FilterHandler to select a single level, and put the StreamHandler inside it 2. Add another StreamHandler with php://stdout as stream 3. The best is to use `logrotate`,...

Here is more info about logrotate https://docs.rackspace.com/support/how-to/understanding-logrotate-utility/ - it's a log rotating utility which is present by default on most linux systems (AFAIK).

Interesting issue.. But if flush() triggers an issue it means something was logged between close() and destruct. Otherwise flush would have nothing to flush and it'd be a noop. So...