spring-projects / spring-projects/spring-boot
Allow structure logging "name already written" errors caused by MDC to be logged as warnings
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 81.5k
- Forks
- 42.7k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 65
Description
As discussed in #45063, currently an MDC name that has already been used will throw an IllegalStateException and prevent that message from being logged at all. It would be better if we allowed the structured logging to continue without the offending element and issued a warning instead.
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
Start by reading the discussion in issue #45063, then locate Spring Boot's structured logging handling for MDC names that have already been used. Trace the IllegalStateException path and the related logging tests, if present. Done means logging continues without the offending element and emits a warning instead of dropping the message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100