mirror of
https://github.com/Seldaek/monolog.git
synced 2026-04-26 08:05:53 +03:00
[GH-ISSUE #716] Allow to use different LogHandler with the same LogLevel #265
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#265
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 (Jan 11, 2016).
Original GitHub issue: https://github.com/Seldaek/monolog/issues/716
Let's say I have a use case in which I use the
SyslogUdpHandleras my standard logger.This logger has the Loglevel
Debugby default.When I have a special usecase, where I want to log specific data into a file using
StreamHandlerwith LogLevelDebugthis is not possible because I have another handler already set for this level.Proposal
Logger::addRecord()exits early which is pretty good actually.But maybe it could be some improvement, to add some extra check if the handlers with the same loglevel are handlers of the same type, so that they would not interfere each other?
Not sure if this is suppressed by purpose, but if so, please let me know.
Cheers
@xabbuh commented on GitHub (Jan 12, 2016):
Isn't the GroupHandler what you are looking for?
@ghost commented on GitHub (Jan 12, 2016):
Thanks a lot!
I did not see this. Seems that could be what I'm looking for.