You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default Monolog is attached to Guzzle clients through its Log plugin. I've found that Symfony 404s are still logged even thought they should be excluded, and I think that's the problem. (I've hit this when using the param converter, but it would happen elsewhere too.)
My understanding is that as the Guzzle exception happens first (and the Log plugin sets it to the ERROR level) it activates the ErrorLevelActivationStrategy.
It would be useful to have the Guzzle exception ignored if it's followed by a Symfony 404.
The text was updated successfully, but these errors were encountered:
By default Monolog is attached to Guzzle clients through its Log plugin. I've found that Symfony 404s are still logged even thought they should be excluded, and I think that's the problem. (I've hit this when using the param converter, but it would happen elsewhere too.)
My understanding is that as the Guzzle exception happens first (and the Log plugin sets it to the ERROR level) it activates the ErrorLevelActivationStrategy.
It would be useful to have the Guzzle exception ignored if it's followed by a Symfony 404.
The text was updated successfully, but these errors were encountered: