Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to drop/ignore lines that don't match a given expression. #1092

Closed
mzs114 opened this issue Oct 1, 2019 · 0 comments · Fixed by #1112
Closed

Option to drop/ignore lines that don't match a given expression. #1092

mzs114 opened this issue Oct 1, 2019 · 0 comments · Fixed by #1112

Comments

@mzs114
Copy link

mzs114 commented Oct 1, 2019

Is your feature request related to a problem? Please describe.
Sometimes the user exactly wants lines that match a particular expression be captured and others ignored/dropped, those lines could be noise/irrelevant for the end user. And/or there are too many patterns in the files and the user is interested in specific one(s).

Describe the solution you'd like
A configuration option(like in packet filters) to drop/ignore lines that don't match the expression in pipeline_stages.

Describe alternatives you've considered
Hypothetically(As loki and promtail don't have #553 yet), write more rules/stages to drop lines with various patterns, if there are multiple patterns to be ignore then this increases the effot for the end user and becomes complex.

Additional context
There are other logging patterns, like that start with '#' as the beginning char(MS IIS) and others which usually include multiline comments in debug levels(Zend PHP server, commercial). In all these cases the user would probably prefer to capture a particular pattern rather than write multi stage pipeline to drop the N patterns.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants