Improve log message level usage (between debug and trace)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- java
- Domain
- observability-sre
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.
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.
- Dominant language
- Java
- Stars
- 8
- Forks
- 4
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing 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.
More from NASA-AMMOS/MMTC
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
NASA-AMMOS/MMTC#117 ·
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
NASA-AMMOS/MMTC#113 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
NASA-AMMOS/MMTC#112 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
NASA-AMMOS/MMTC#106 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
NASA-AMMOS/MMTC#104 ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
apache/rocketmq-dashboard#6331 ·
Maintainers usually reply within 5 days
-
status: team-only type: dependency-upgrade
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
spring-projects/spring-boot#52143 · 1 comment ·
Maintainers usually reply within 1 day
-
area/frontend good first issue kind/cooldown
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
kestra-io/kestra#20704 · 1 comment ·
Maintainers usually reply within 1 day