Improve log message level usage (between debug and trace)
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 8
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Stan has given feedback that MMTC's debug-level logging is quite prolific and makes it hard to find the information he's looking for. It could be an option to move some debugging logging to the 'trace' level to assist with this. Work with him, and possibly others, to decide what to adjust.
Contributor guide
No contributing guide indexed for this repository
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, or entry points are named. Start by locating MMTC's debug-level logging and understanding the available trace level, then discuss with Stan and other users which messages should move. Done means the logging levels reflect an agreed decision and the prolific debug output is reduced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability-sre
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100