Sleuth overrides a user's logging.pattern.level when it's configured in bootstrap.yml
See original GitHub issueDescribe the bug
Sleuth’s default logging.pattern.level should not apply when the user has configured their own, however it is taking precedence when the user has configured their own in bootstrap.yml. Please see https://github.com/spring-projects/spring-boot/issues/25418 for details. I’m not sure if this is a Sleuth problem or a more general Spring Cloud Commons problem.
Sample There’s a sample in the Spring Boot issue along with some initial analysis.
Issue Analytics
- State:
- Created 3 years ago
- Comments:17 (15 by maintainers)
Top Results From Across the Web
Spring Cloud Sleuth
Minimum logging level to be presented in the console logs--> <level>DEBUG</level> </filter> ... set the spring.application.name property in bootstrap.yml .
Read more >Sleuth is overriding logging.pattern.level configured in ...
I have started integrating Spring cloud Sleuth into our project to generate automatic trace-id and span-id. The project is built on Spring ...
Read more >Add Spring Boot Profile to Sleuth/Zipkin logs - Stack Overflow
yml file, the above log-pattern just prints "bootstrap" as application name. You're mixing all possible patterns from what I see :P.
Read more >Configure Spring Boot logging with application.yml
To set a different logging level for any logger, add in your application.yml file the log levels under the tree logging > level....
Read more >spring-cloud-sleuth - Gitee
Other logging systems have to configure their own formatter to get the same result. The default is as follows: logging.pattern.level set to %5p...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I’ve added a parameter
spring.sleuth.default-logging-pattern-enabledwhich is turned on by default. By setting it tofalsethe default Sleuth pattern will not be set.@marcingrzejszczak
I’ve raised a PR to reintroduce the configuration back https://github.com/spring-cloud/spring-cloud-sleuth/pull/2196
Please let me know your thoughts 😃