stackabletech / stackabletech/operator-rs
Log4j logs are filtered by both appender and logger
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 167
- Forks
- 19
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 9
Description
Affected version
No response
Current and expected behavior
Currently, setting the root (or sublogger) log level for a log4j-based container doesn't really do anything, because we also filter the logs for each appender.
This makes sense as a feature to opt into, but at least I have burned a lot of time trying to figure out why my debug logs were still missing.
Possible solution
No response
Additional context
No response
Environment
No response
Would you like to work on fixing this bug?
None
Contributor guide
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.
Research direction
No files, tests, entry points, or implementation proposal are named in the issue. Start by locating the Log4j-based container logging configuration and trace how logger and appender levels are applied; done means the root or sublogger level behaves as expected without unexpected duplicate filtering, with coverage for the chosen behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100