spring boot, logback and logging.config property

Question

I am implementing logging in a spring boot project with logback library. I want to load different logging configuration files according to my spring profiles (property 'spring.pofiles.active'). I have 3 files : logback-dev.xml, logback-inte.xml and logback-prod.xml. I am using spring boot version 1.2.2.RELEASE.

As you can read in spring boot documentation:

The various logging systems can be activated by including the appropriate libraries on the classpath, and further customized by providing a suitable configuration file in the root of the classpath, or in a location specified by the Spring Environment property logging.config. (Note however that since logging is initialized before the ApplicationContext is created, it isn’t possible to control logging from @PropertySources in Spring @Configuration files. System properties and the conventional Spring Boot external configuration files work just fine.)

So I tried to set 'logging.config' property in my application.properties file:

logging.config=classpath:/logback-${spring.profiles.active}.xml 

But when i start my application, my logback-{profile}.xml is not loaded...

I think logging is a common problem that all projects using spring boot have encountered. Am I on the right track with the above approach? I have other solutions that work, but I find them not as elegant (conditional parsing with Janino in logback.xml file or command line property).

Answer 1

I found a solution and I understood why spring doesn't use my 'logging.config' property defined in the application.properties file.

Solution and explanation :

When initializing logging, spring Boot only looks in classpath or environment variables.

The solution I used was to include a parent logback.xml file that included the right logging config file according to the spring profile.

logback.xml :

<configuration>     <include resource="logback-${spring.profiles.active}.xml"/> </configuration> 

logback-[profile].xml (in this case, logback-dev.xml) :

<included>      <!-- put your appenders -->     <appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender">     <!-- encoders are assigned the type      ch.qos.logback.classic.encoder.PatternLayoutEncoder by default -->        <encoder>            <pattern>%d{ISO8601} %p %t %c{0}.%M - %m%n</pattern>            <charset>utf8</charset>         </encoder>     </appender>      <!-- put your loggers here -->     <logger name="org.springframework.web" additivity="false" level="INFO">         <appender-ref ref="CONSOLE" />     </logger>      <!-- put your root here -->     <root level="warn">         <appender-ref ref="CONSOLE" />     </root>  </included> 

Note : 'spring.profiles.active' has to be set in command line arguments when starting the app. E.G for JVM properties : -Dspring.profiles.active=dev

Ref docs :

• http://docs.spring.io/spring-boot/docs/current/reference/html/howto-logging.html
• http://docs.spring.io/spring-boot/docs/current/reference/html/boot-features-logging.html
• http://docs.spring.io/spring-boot/docs/0.5.0.M3/api/org/springframework/boot/context/initializer/LoggingApplicationContextInitializer.html

Edit (multiple active profiles) : In order to avoid multiple files, we could use conditional processing which requires Janino dependency (setup here), see conditional documentation. With this method, we can also check for multiple active profiles at the same time. E.G (I did not test this solution, so please comment if it does not work):

<configuration>      <if condition='"${spring.profiles.active}".contains("profile1")'>         <then>          <!-- do whatever you want for profile1 -->         </then>     </if>      <if condition='"${spring.profiles.active}".contains("profile2")'>         <then>          <!-- do whatever you want for profile2 -->         </then>     </if>      <!-- common config -->  </configuration> 

See javasenior answer for another example of a conditional processing.