mirror of
https://github.com/Seldaek/monolog.git
synced 2026-04-26 16:15:49 +03:00
[GH-ISSUE #1608] How DeduplicationHandler works? #687
Labels
No labels
Bug
Documentation
Feature
Needs Work
Support
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/monolog#687
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ghost on GitHub (Nov 10, 2021).
Original GitHub issue: https://github.com/Seldaek/monolog/issues/1608
Hello!
Have I understood correctly, that
DeducpliationHandlerlets all log messages through but deduplicates only messages that have level greater or equal to what has been set toDeduplicationHandler::$deduplicationLevel?I.e. if I have set deduplication level to
errorand I have 10debugmessages and 10errormessages, all 10debugmessages are passed to wrapped handler and only 1errormessage?Br, Miika
@phroggar commented on GitHub (Feb 17, 2022):
Yes the dedup handler will only look on the level supplied (or greater). Lower levels are passed through without deduplication.
@Seldaek commented on GitHub (Mar 7, 2022):
Yeah the point is really to use this in combination with a FingersCrossedHandler IMO so that the dumping of debug info etc only happens when a deduplicated error reaches the FingersCrossedHandler. But this may depend on your use case.