@@ -1025,7 +1025,7 @@ exceptions
10251025
10261026**type **: ``array ``
10271027
1028- Defines the:ref: `log level </logging >` and HTTP status code applied to the
1028+ Defines the:ref: `log level </logging >`, :ref: ` log channel < /logging >` and HTTP status code applied to the
10291029exceptions that match the given exception class:
10301030
10311031..configuration-block ::
@@ -1038,6 +1038,7 @@ exceptions that match the given exception class:
10381038Symfony\Component\HttpKernel\Exception\BadRequestHttpException :
10391039log_level :' debug'
10401040status_code :422
1041+ log_channel :' custom_channel'
10411042
10421043code-block ::xml
10431044
@@ -1055,6 +1056,7 @@ exceptions that match the given exception class:
10551056class =" Symfony\Component\HttpKernel\Exception\BadRequestHttpException"
10561057log-level =" debug"
10571058status-code =" 422"
1059+ log-channel =" custom_channel"
10581060 />
10591061<!-- ...-->
10601062 </framework : config >
@@ -1070,9 +1072,14 @@ exceptions that match the given exception class:
10701072 $framework->exception(BadRequestHttpException::class)
10711073 ->logLevel('debug')
10721074 ->statusCode(422)
1075+ ->logChannel('custom_channel')
10731076 ;
10741077 };
10751078
1079+ versionadded ::7.3
1080+
1081+ The ``log_channel `` option was introduced in Symfony 7.3.
1082+
10761083The order in which you configure exceptions is important because Symfony will
10771084use the configuration of the first exception that matches ``instanceof ``:
10781085