diff --git a/logging.rst b/logging.rst
index dd4d8a87c62..6804a19a82e 100644
--- a/logging.rst
+++ b/logging.rst
@@ -341,9 +341,14 @@ Learn more
     logging/channels_handlers
     logging/formatter
     logging/processors
-    logging/monolog_regex_based_excludes
+    logging/monolog_exclude_http_codes
     logging/monolog_console
 
+.. toctree::
+    :hidden:
+
+    logging/monolog_regex_based_excludes
+
 .. _Monolog: https://github.com/Seldaek/monolog
 .. _LoggerInterface: https://github.com/php-fig/log/blob/master/Psr/Log/LoggerInterface.php
 .. _`logrotate`: https://github.com/logrotate/logrotate
diff --git a/logging/monolog_regex_based_excludes.rst b/logging/monolog_regex_based_excludes.rst
index 0ab3269c8d6..3a718dd0680 100644
--- a/logging/monolog_regex_based_excludes.rst
+++ b/logging/monolog_regex_based_excludes.rst
@@ -6,6 +6,12 @@
 How to Configure Monolog to Exclude 404 Errors from the Log
 ===========================================================
 
+.. tip::
+
+    Read :doc:`/logging/monolog_exclude_http_codes` to learn about a similar
+    but more generic feature that allows to exclude logs for any HTTP status
+    code and not only 404 errors.
+
 Sometimes your logs become flooded with unwanted 404 HTTP errors, for example,
 when an attacker scans your app for some well-known application paths (e.g.
 `/phpmyadmin`). When using a ``fingers_crossed`` handler, you can exclude