Set logs level to WARN for production image - #3941
Conversation
There was a problem hiding this comment.
Pull request overview
Updates Logback logger levels to reduce verbosity (intended to set production logging to WARN per PR title).
Changes:
- Changed several framework/package loggers (
org.mapfish,com.codahale,org.springframework,org.apache,org.hibernate) fromDEBUGtoWARNincore/src/main/resources/logback.xml.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| <logger name="org.mapfish" level="WARN" /> | ||
| <logger name="com.codahale" level="WARN" /> | ||
| <logger name="org.springframework" level="WARN" /> | ||
| <logger name="org.apache" level="WARN" /> | ||
| <logger name="org.hibernate" level="WARN" /> |
There was a problem hiding this comment.
PR title mentions changing log level for the production image, but the Docker/Tomcat image appears to use core/docker/usr/local/tomcat/conf/logback.xml (see core/docker/usr/local/tomcat/bin/setenv.sh setting -Dlogback.configurationFile=.../conf/logback.xml). Changes in core/src/main/resources/logback.xml likely won’t affect production container logging; consider moving/applying the level change to the Docker logback config or its env-driven defaults instead.
|
Not used in a production environment => closing |
No description provided.