Do not execute log processors below configured log level
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- go
- Domain
- observability
Research direction
The issue provides only a YAML reproduction; locate the log processor and configured log-level handling first. Verify that the fields mapping is not evaluated when its level is below the active threshold while the pipeline remains unchanged, then run the relevant processor tests.
Written by the indexing model from the issue text.
Description
Currently, log processors always execute, even if their log level is lower than the currently set log level.
Consider the configuration below. If the current log level is not TRACE, I would not expect the mapping to execute.
input:
generate:
mapping: |
root = {}
pipeline:
processors:
- log:
level: TRACE
fields_mapping: |
root = throw("foo")
output:
stdout: {}
This would be a minor performance improvement, and matches how log formatting works in other languages (e.g. Python).
The log processor states that the message remains unchanged, so skipping its execution would have no effect on the pipeline.
- Dominant language
- Go
- Stars
- 571
- Forks
- 121
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 15
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from redpanda-data/benthos
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
redpanda-data/benthos#404 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
redpanda-data/benthos#503 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
redpanda-data/benthos#502 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 72/100
redpanda-data/benthos#481 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
redpanda-data/benthos#469 ·
Maintainers usually reply within 1 day
All issues in redpanda-data/benthos
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
gruntwork-io/boilerplate#329 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
prime-radiant-inc/evener#3291 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Netcracker/qubership-apihub-backend#582 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day