Add options to filter logs by --logLevel and --context #271
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
tw4l
force-pushed
the
issue-270-filter-logs
branch
from
accf283 to
42cd9f9
Compare
tw4l
force-pushed
the
issue-270-filter-logs
branch
from
42cd9f9 to
7c899d5
Compare
ikreymer
approved these changes
Apr 1, 2023
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.
This PR adds
--logLeveland--contextCLI arguments which each take a comma-separated list of values to filter the logs by. If one or both arguments are provided, only log lines which match the specified log level and/or context will be logged. The PR also includes a new test which runs a crawl and verifies that all lines in the resulting log file(s) match the expected logLevel/contexts.