8000 Document new Monolog HTTP code exclusion feature by simshaun · Pull Request #8235 · symfony/symfony-docs · GitHub
[go: up one dir, main page]

Skip to content

Document new Monolog HTTP code exclusion feature #8235

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.

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

Merged
merged 6 commits into from
May 15, 2018
Merged
Changes from 1 commit
Commits
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
Prev Previous commit
Added the versionadded directive
  • Loading branch information
javiereguiluz authored May 15, 2018
commit 30cc7d42abdb9aeaa176689d3536237422304fe9
4 changes: 4 additions & 0 deletions logging/monolog_exclude_http_codes.rst
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,10 @@
How to Configure Monolog to Exclude Specific HTTP Codes from the Log
====================================================================

..versionadded:: 4.1
The ability to exclude log messages based on their status codes was
introduced in Symfony 4.1 and MonologBundle 3.3.

Sometimes your logs become flooded with unwanted HTTP errors, for example,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need a versionadded here:

..versionadded:: 4.1
    The ability to exclude status codes was introduced in Symfony 4.1 and MonologBundle 3.3.

I'm guessing on the 3.3 part for MonologBundle, but unless something super strange happens, that should be true.

403s and 404s. When using a ``fingers_crossed`` handler, you can exclude
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Quick question: is the mention 80EA of the fingers_crossed handler just an example or does this feature only work with that specific handler?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I based the feature off of NotFoundActivationStrategy, which is only for fingers_crossed

logging these HTTP codes based on the MonologBundle configuration:
Expand Down
0