looks like Fabbot is broken.

Anyway, this patch is much better, because it actually does the work. BTW, introducing the methodreset() without calling the parent was a BC break, isn't ?

But it is still not perfect. ATM we rely on the fact that processors and handlers are shared among all loggers. But there is one logger per channel. So when we callLogger::reset(), we call it on only one logger. Not all!

Let me explain this a bit more. Let's consider this config:

monolog:handlers:main:type:fingers_crossedaction_level:errorhandler:bufferbuffer_size:50channels:["!php"]buffer:type:bufferhandler:filefile:type:streampath:'%kernel.logs_dir%/%kernel.environment%.log'php:type:fingers_crossedaction_level:errorhandler:php_filebuffer_size:50channels:["php"]php_file:type:streampath:'%kernel.logs_dir%/%kernel.environment%-php.log'

And with this PHP script:

<?phprequire__DIR__.'/vendor/autoload.php';$k =newAppKernel('dev',true);$k->boot();$c =$k->getContainer();// (I had to patch SF to make theses services public)$c->get('monolog.logger.php')->debug('debug from php - XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX');$c->get('monolog.logger.consumer')->debug('debug from consumer - YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY');$c->get('monolog.logger.consumer')->reset();dump(['logger php' =>$c->get('monolog.logger.php'),'logger consumer' =>$c->get('monolog.logger.consumer')]);

We can simulate our issue. In my consumer, I gotmonolog.logger.consumer logger. And when I callreset() it's well reset. But themonolog.logger.php is not reset :/

In my application, I don't have this issue because our configuration is more classical. But I know some people are doing this kind of configuration. We need to know that :)

Isn't it something we can do on 3.4?

@fabpot TheLogger::reset() did not exist in3.4. So I guess it's not possible as it would be a new feature. on 4.2 it's a bug fix.

Thank you@lyrixx.