Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FrameworkBundle] Document log_channel #20818

Merged
merged 1 commit into from
Mar 28, 2025
Merged

[FrameworkBundle] Document log_channel #20818

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion reference/configuration/framework.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1025,7 +1025,7 @@ exceptions

**type**: ``array``

Defines the :ref:`log level </logging>` and HTTP status code applied to the
Defines the :ref:`log level </logging>`, :ref:`log channel </logging/channels_handlers>` and HTTP status code applied to the
exceptions that match the given exception class:

.. configuration-block::
Expand All @@ -1038,6 +1038,7 @@ exceptions that match the given exception class:
Symfony\Component\HttpKernel\Exception\BadRequestHttpException:
log_level: 'debug'
status_code: 422
log_channel: 'custom_channel'

.. code-block:: xml

Expand All @@ -1055,6 +1056,7 @@ exceptions that match the given exception class:
class="Symfony\Component\HttpKernel\Exception\BadRequestHttpException"
log-level="debug"
status-code="422"
log-channel="custom_channel"
/>
<!-- ... -->
</framework:config>
Expand All @@ -1070,9 +1072,14 @@ exceptions that match the given exception class:
$framework->exception(BadRequestHttpException::class)
->logLevel('debug')
->statusCode(422)
->logChannel('custom_channel')
;
};

.. versionadded:: 7.3

The ``log_channel`` option was introduced in Symfony 7.3.

The order in which you configure exceptions is important because Symfony will
use the configuration of the first exception that matches ``instanceof``:

Expand Down