Repository navigation
Filter entries by level and pattern - #2
Merged
Merged
Conversation
This was referenced Oct 22, 2026
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
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.
Before: every line of a log was printed, so finding the errors in a busy service meant piping through
grepand losing level colors and stack traces along the way.After:
relay-logs -l warn app.logshows only warnings and worse,-gkeeps lines matching a pattern, and-xdrops lines matching one. They work with-f, sorelay-logs -f -l error -x /health api.logfollows only the errors that matter. Indented lines such as stack frames stay with the entry above them, so an error keeps its trace even though the frames have no level of their own.Patterns are regular expressions and ignore case unless they contain an uppercase letter.
How:
createFilterbuilds a predicate from the options and remembers, per source, whether the last entry was shown so continuation lines follow it. Invalid patterns and unknown level names are reported as usage errors with exit code 2.This branch is stacked on #1; please merge that first.