@Nyholm yeah, I agree with@derrabus comment. That's why I did not change the current Symfony behavior.

But now, everything is configurable, that's what many people want.

About a solution in pure PHP to decide or not... I'm not really convinced. The solution I propose fit my needs and is simple to use. Do you have real use case where it does not fit and you would need PHP to configure it?

@Nyholm I have fixed your comments, thanks.

I think the PR is ready now

Hello @symfony/mergers

The initial issue got 8 👍🏼, 4 ❤️ and, this PR got 5 ❤️ and@dunglas commented "A big +1 on my side." on the issue.

So without feedback, I'm planning to merge this PR by the end of the month, before the feature freeze.
If you are against it, it's time to raise your voice :)

Thank you@lyrixx.

Can you start documenting this in docs?

I'll do that ASAP :)

It would have been nice to have system in place, to convert these exceptions in code, instead of just config. This way it might be possible to log for example a request to/missing/url aserror, while/favicon.ico is not logged at all.

This way it's all or nothing.

@lyrixx Is there any plan for this feature to cover errors handled in ErrorHandler ? In our app, because of huge exports of data, we may have either OutOfMemoryError or FatalError (with a message containing "Maximum execution", that represents timeouts) that we don't want to see logged with a "critical" level and have dedicated HTTP status codes (507 for OutOfMemory and 504 for timeouts). But using this mapping in the configuration for OutOfMemoryError doesn't change the criticality of the logged Fatal Error and I don't see how I could filter the FatalError only with the custom message.

For what it's worth I did try to fix the issue found in#42244 (comment) but could not. I can't say I'm too happy about it because it means the feature really doesn't work as advertised. But given the lack of solution the best that may be done at this point is to document it.

@theofidry FYI this feature was adjusted here#44649, so your previous comment about the status code for HTML response/page should be ok now

wow cool, thanks for the notif

I'm testing a feature to log theCars\Exceptions\CarsNotFoundException exception as aninfo message with a 404 status code, but it's not working as expected.

This is my framework exception configuration:

framework:exceptions:Cars\Exceptions\CarsNotFoundException:log_level:infostatus_code:404

However, the logger is marking it as CRITICAL:

[2024-01-05T11:51:44.155556+01:00] php.CRITICAL: Uncaught Exception: Not found car with id9991057X1 {"exception":"[object] (Symfony\\Component\\HttpKernel\\Exception\\HttpException(code:0): Not found car with id9991057X1 at /var/www/code/Cars/vendor/symfony/http-kernel/EventListener/ErrorListener.php:70)\n[previous exception] [object] (Cars\\Exceptions\\CarsNotFoundException(code:404): Not found cars with id9991057X1"} []

I want to configure the exception to log asinfo with a 404 status code. Currently, my code throwsCars\Exceptions\CarsNotFoundException, and thekernel.exception listener changes it toSymfony\Component\HttpKernel\Exception\HttpException. I don't want to log allHttpException instances as info, only theCarsNotFoundException

framework:exceptions:Cars\Exceptions\CarsNotFoundException:log_level:infostatus_code:404Symfony\Component\HttpKernel\Exception\HttpException:log_level:infostatus_code:404

Can I achieve this without changingHttpException ?

Thank you.

Please open a new issue with the problem and add a reference to this PR, thanks