Tomcat 8下为多个Spring Boot Web应用配置独立外部日志方案咨询

Got it, let's break down how to get individual Logback configs for each of your Spring Boot WARs on Tomcat 8—no more sharing a single global setup, and no need to package log configs into your WARs. Here are three reliable approaches:

1. Set logging.config Per Tomcat Context #

Tomcat lets you define context-specific parameters for each deployed app, which takes precedence over global system properties. Here's how to do it:

• For each application, create a context XML file in conf/Catalina/localhost/[your-app-name].xml (replace [your-app-name] with the actual app context path, e.g., myapp.xml).
• Add this configuration to the file:

<Context docBase="/absolute/path/to/your/app.war">
    <!-- Point to the external logback config for this app -->
    <Parameter name="logging.config" value="/path/to/your/app-specific-logback.xml" override="false"/>
</Context>

Spring Boot will pick up this context parameter instead of any global -Dlogging.conf setting, so each app uses its own config. The override="false" ensures your external config isn't overwritten by anything in the WAR.

2. Use Environment Variables with Spring Boot's Configuration Priority #

If you prefer using environment variables over context parameters, you can leverage Spring Boot's property resolution:

• First, add this line to your Spring Boot app's application.properties (or application.yml)—this tells Spring Boot to look for an environment variable for the log config, with a fallback if it's not set:

logging.config=${APP_LOG_CONFIG:/default/log/path/logback.xml}

• Then, for each app, add an environment variable to its context XML file (conf/Catalina/localhost/[your-app-name].xml):

<Context docBase="/absolute/path/to/your/app.war">
    <Environment name="APP_LOG_CONFIG" value="/path/to/your/app-specific-logback.xml" type="java.lang.String" override="false"/>
</Context>

This way, each app gets its own log config path via the environment variable, and you don't need to touch global Tomcat settings.

3. Centralize a Base Logback Config with App-Specific Includes #

If you want a shared base config but still need app-specific tweaks, you can use Logback's <include> tag:

• Place a base logback.xml in Tomcat's lib directory. This will act as the default for all apps, and it can include app-specific sections:

<configuration>
    <!-- Shared global config (e.g., appenders, levels) -->
    <appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender">
        <encoder>
            <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</pattern>
        </encoder>
    </appender>

    <!-- Include app-specific config -->
    <include resource="${APP_LOG_INCLUDE}"/>

    <root level="info">
        <appender-ref ref="CONSOLE"/>
    </root>
</configuration>

• Then, set the APP_LOG_INCLUDE environment variable in each app's context XML to point to its specific config file (e.g., /path/to/app1-logback.xml), which can override or add to the base config.

Key Notes to Remember #

• Exclude logback.xml from your WAR: Make sure you don't package the config into your WAR file. If using Maven, add this to your pom.xml to exclude it:

<build>
    <plugins>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-war-plugin</artifactId>
            <configuration>
                <excludes>
                    <exclude>logback.xml</exclude>
                </excludes>
            </configuration>
        </plugin>
    </plugins>
</build>

• File Permissions: Ensure Tomcat's running user has read access to all external logback config files.
• Spring Boot Version Check: Since you're using Tomcat 8, you're likely on Spring Boot 2.x—all these approaches work reliably with 2.x versions.

内容的提问来源于stack exchange，提问作者Leonard Saers