This repository was archived by the owner on Dec 19, 2020. It is now read-only.
Add a new filter that matches against a logger name #3
Conversation
This file contains hidden or 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
This logging filter matches a logger name. Included is an example of its use, the filter itself, and a unit test for this functionality.
|
@rgoers I have created a merge branch that incorporates these changes into the develop branch. If you edit the pull request to point at the creature-logger-name-filter branch in my repository, it should be able to test and merge. I already merged it into develop on mine. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
This patch provides a new logging filter, similar to the existing string matcher, that matches against a logger name. It provides options for case sensitivity and exact matching, as well as the standard acceptOnMatch and stringToMatch parameters. Unit tests and documentation are included.
My use case for this is included in the documentation; I've found it useful to log events from specific sources to their own logfiles, so I can have a standalone log for payment gateways, SMS sending, etc. Sometimes this is for ease of debugging; sometimes it makes integration with other tools like Munin easier.