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

[processor/filter] extend log filtering capabilities with body and severity #9235

Closed
pmm-sumo opened this issue Apr 12, 2022 · 4 comments
Closed
Assignees
Labels

Comments

@pmm-sumo
Copy link
Contributor

Is your feature request related to a problem? Please describe.

Filter processor currently has very limited log record filtering capabilities (only by matching a record basing on some attributes or resources). We could easily extend it to filter by body or severity though.

Describe the solution you'd like

filterlog already has support for matching log body and upcoming one for matching log severity

This code is shared among several components, including filter processor. We could leverage it and add easily add a capability for filtering log records basing on the matching log body or severity.

@github-actions
Copy link
Contributor

Pinging code owners: @boostchicken @pmm-sumo

@cpheps
Copy link
Contributor

cpheps commented Jul 29, 2022

@pmm-sumo I'd like to volunteer to take this if it's not already being worked on.

@github-actions
Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Nov 10, 2022
@github-actions
Copy link
Contributor

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants