Less verbose logging
Open
- Dominant language
- Java
- Stars
- 6.1k
- Forks
- 1.5k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 189
Description
It's very difficult to diagnose the cause of a test failure in CI because of the very verbose logging which is almost always irrelevant to the cause of failure. A lot of the culprits come come from Helix, but some Pinot logging should be moved from WARN to DEBUG.
Contributor guide
Research direction
Start by reproducing the CI test-failure output and identifying which Helix messages and Pinot WARN logs make it unnecessarily verbose. The work is done when irrelevant logging is reduced without hiding information needed to diagnose test failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- ci-cd, observability
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100