Skip to content

Commit 091695a

Browse files
committed
Fixed build and link to the recommended article to exclude logs
1 parent c30ff06 commit 091695a

File tree

2 files changed

+12
-1
lines changed

2 files changed

+12
-1
lines changed

logging.rst

+6-1
Original file line numberDiff line numberDiff line change
@@ -341,9 +341,14 @@ Learn more
341341
logging/channels_handlers
342342
logging/formatter
343343
logging/processors
344-
logging/monolog_regex_based_excludes
344+
logging/monolog_exclude_http_codes
345345
logging/monolog_console
346346

347+
.. toctree::
348+
:hidden:
349+
350+
logging/monolog_regex_based_excludes
351+
347352
.. _Monolog: https://github.com/Seldaek/monolog
348353
.. _LoggerInterface: https://github.com/php-fig/log/blob/master/Psr/Log/LoggerInterface.php
349354
.. _`logrotate`: https://github.com/logrotate/logrotate

logging/monolog_regex_based_excludes.rst

+6
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,12 @@
66
How to Configure Monolog to Exclude 404 Errors from the Log
77
===========================================================
88

9+
.. tip::
10+
11+
Read :doc:`/logging/monolog_exclude_http_codes` to learn about a similar
12+
but more generic feature that allows to exclude logs for any HTTP status
13+
code and not only 404 errors.
14+
915
Sometimes your logs become flooded with unwanted 404 HTTP errors, for example,
1016
when an attacker scans your app for some well-known application paths (e.g.
1117
`/phpmyadmin`). When using a ``fingers_crossed`` handler, you can exclude

0 commit comments

Comments
 (0)