[SecurityBundle] Use "event" monolog channel in traceable firewall event dispatcher #54032
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hey! Thanks for your PR. You are targeting branch "7.1" but it seems your PR description refers to branch "7.1 or 7.0". Cheers! Carsonbot |
fabpot
approved these changes
Mar 17, 2024
fabpot
force-pushed
the
traceable-firewall-eventdispatcher
branch
from
575b929
to
3995c71
Compare
|
Thank you @danielburger1337. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I think since #49021 was merged, security events in debug mode are logged inside the "app" (default) channel.
This is very annoying in an API use case as every request generates about 10 useless log entries.
This PR changes the monolog channel of the traceable event dispatcher to
eventand also tags it withkernel.reset. This matches the behavior ofdebug.event_dispatcher.