Overriding logging properties like FILE_LOG_PATTERN

[marceloverdijk]

Feature request for adding support for overriding logging properties via application.properties/yaml.

E.g. I want to easily override the FILE_LOG_PATTERN property.
To define this in the application.properties/yaml also gives the benefit that I can change it per environment.

Boot already offers

# LOGGING
logging.path=/var/logs
logging.file=myapp.log
logging.config= # location of config file (default classpath:logback.xml for logback)
logging.level.*= # levels for loggers, e.g. "logging.level.org.springframework=DEBUG" (TRACE, DEBUG, INFO, WARN, ERROR, FATAL, OFF)

Something like below maybe?

logging.property.FILE_LOG_PATTERN=

Reference: http://stackoverflow.com/questions/26629197/overriding-the-file-log-pattern-if-possible-per-env

[backs999]

This would be very useful as I also have just come across the need to override the pattern for our logging indexer +1

[joensson]

+1 - This would indeed be very useful. We have the same need - and would also like to set other properties for use in logback config in the same manner.

[khoubyari]

+1

[philwebb]

Seems like a popular request. I'll assign to 1.2 and take a look but we are really near GA so it might need to be pushed back to 1.3.

[marceloverdijk]

Since I raised this feature request I needed to log to 2 separate files. 1 standard log file (with a customized format containing MDC info) but also 1 log file to be used for Logstash/Elasticsearch with custom layout class.
Would it also be possible to configure multiple file appenders using these properties?

[philwebb]

@marceloverdijk Sounds like a fairly complex scenario so it probably won't be possible with the properties. Have you tried defining your own logback.xml file? There are a couple imports that you can use (see this example).

[marceloverdijk]

Yes I'm using a custom logback.xml now.
I only wished I could have a logback.xml per env.

Btw I think it should be possible to define multiple appenders via properties. With standard log4j properties file this is also possible. Thinking of it I wonder if it would be possible to define log4j.* properties (in applucation properties) and use them to initiate log4j? Just thinking loud to see options for customizations and per env config.

[joensson]

Have not tried it myself - but for environment specific logback configurations I think it is possible to do that using logback includes.

Create a 'master' logback configuration file that includes another environment specific logback-staging.xml - that has root tag 'included'.

logback-master.xml:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <include resource="logback-${LOGBACK_ENV}.xml"/>
    <include resource="org/springframework/boot/logging/logback/base.xml"/>
...
<!-- do something with the MY_PROPERTY value -->
...
</configuration>

logback-test.xml:

<?xml version="1.0" encoding="UTF-8"?>
<included>
    <property name="MY_PROPERTY" value="test"/>
...
</included>

When launching your application set the LOGBACK_ENV system property, e.g. System.setProperty("LOGBACK_ENV", "test") (this will of course not be necessary when the current issue has been fixed - at that time we can simple set a property in application.properties instead) and if the file exists you should see a log line from logback:
INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback-test.xml] at ...

• almost lige we did in Spring in the good old pre-profile days when wanting different beans/properties per environment.

[philwebb]

I'm afraid I need to push this back for now :(

[marceloverdijk]

Hopefully another day maybe :-)

On 09 Dec 2014, at 19:31, Phil Webb notifications@github.com wrote:

I'm afraid I need to push this back for now :(

—
Reply to this email directly or view it on GitHub.

[ljramones]

+1
agreed, this is a good feature.