Add %kvp to default logging pattern to support SLF4J 2.x fluent key-value logging #47162
+2
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Spring Boot 3 uses SLF4J 2.x, which introduced the fluent logging API (
log.atInfo().addKeyValue(...).log(...)
).Currently, when using the default logging pattern, the key–value pairs are silently ignored because %kvp is not included in the log pattern.
This PR updates the default console and file logging pattern to append %kvp after the log message (%m).
Why
Developers using SLF4J’s fluent API expect key–value pairs to be visible without custom Logback configuration.
Aligns Spring Boot defaults with SLF4J 2.x features.
Provides more observability by making structured key–value logging visible out-of-the-box.
Changes
Before:
After: