如何在 spring boot 中关闭调试日志消息

声明:本页面是StackOverFlow热门问题的中英对照翻译,遵循CC BY-SA 4.0协议,如果您需要使用它,必须同样遵循CC BY-SA许可,注明原文地址和作者信息,同时你必须将它归于原作者(不是我):StackOverFlow 原文地址: http://stackoverflow.com/questions/35353869/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me): StackOverFlow

提示:将鼠标放在中文语句上可以显示对应的英文。显示中英文
时间:2020-09-08 00:58:56  来源:igfitidea点击:

how turn off debug log messages in spring boot

springspring-bootlog4j

提问by Jim C

I read in spring boot docs (https://docs.spring.io/spring-boot/docs/current/reference/html/boot-features-logging.html)

我在 spring boot docs ( https://docs.spring.io/spring-boot/docs/current/reference/html/boot-features-logging.html) 中阅读

you can also specify debug=true in your application.properties"

您还可以在 application.properties 中指定 debug=true"

So I guess I can turn off the debug logs by adding debug=false in application.properties. I did it but unfortunately it didn't work. Then I read in same doc

所以我想我可以通过在 application.properties 中添加 debug=false 来关闭调试日志。我做到了,但不幸的是它没有用。然后我在同一个文档中阅读

The logging system is initialized early in the application lifecycle and as such logging properties will not be found in property files loaded via @PropertySourceannotations"

日志系统在应用程序生命周期的早期初始化,因此在通过@PropertySource注释加载的属性文件中找不到这样的日志属性”

and

"Since logging is initialized before the ApplicationContextis created, it isn't possible to control logging from @PropertySourcesin Spring @Configurationfiles"

“由于日志记录是在ApplicationContext创建之前初始化的,因此无法从@PropertySourcesSpring@Configuration文件中控制日志记录”

and

"When possible we recommend that you use the -spring variants for your logging configuration" so I added a file named log4j-spring.propertiesin src/main/resources.

“如果可能的话,我们建议您使用-spring变种为您的日志配置”所以我加了一个文件名为log4j-spring.propertiessrc/main/resources

In such file I added debug=false(only this line and nothing else) but I am still seeing all "current date" [main] DEBUG ... messages. So, my question is how can I turn off the debug messages in my Spring Boot Application as I will deploy to the application to production. Is there a recommend way to reach this via maven?

在这样的文件中,我添加了debug=false(只有这一行,没有其他内容),但我仍然看到所有“当前日期”[main] DEBUG ... 消息。所以,我的问题是如何关闭 Spring Boot 应用程序中的调试消息,因为我将部署到应用程序以进行生产。有没有推荐的方法可以通过 maven 达到这个目的?

***** Added in Feb 12th

***** 添加于 2 月 12 日

The two main methods: 1)By using AnnotationConfigApplicationContext:

两种主要方法: 1)通过使用 AnnotationConfigApplicationContext:

public class DemoAppNoBoot {
       public static void main(String[] args) {
              AnnotationConfigApplicationContext context = new AnnotationConfigApplicationContext(
                           BatchConfiguration.class);
              JobLauncher jobLauncher = (JobLauncher) context.getBean("jobLauncher");
              Job job = (Job) context.getBean("job");
               try {
                     JobExecution execution = jobLauncher.run(job, new JobParameters());
              } catch (Exception e) {
                     e.printStackTrace();
              }
       }
}

Snippet output:

片段输出:

08:26:18.713 [main] DEBUG o.s.core.env.StandardEnvironment - Adding [systemProperties] PropertySource with lowest search precedence
08:26:18.744 [main] DEBUG o.s.core.env.StandardEnvironment - Adding [systemEnvironment] PropertySource with lowest search precedence
08:26:18.744 [main] DEBUG o.s.core.env.StandardEnvironment - Initialized StandardEnvironment with PropertySources [systemProperties,systemEnvironment]
08:26:18.947 [main] INFO  o.s.c.a.AnnotationConfigApplicationContext - Refreshing org.springframework.context.annotation.AnnotationConfigApplicationContext@532760d8: startup date [Fri Feb 12 08:26:18 CST 2016]; root of context hierarchy
08:26:18.947 [main] DEBUG o.s.c.a.AnnotationConfigApplicationContext - Bean factory for org.springframework.context.annotation.AnnotationConfigApplicationContext@532760d8: org.springframework.beans.factory.support.DefaultListableBeanFactory@50b494a6: defining beans [org.springframework.context.annotation.internalConfigurationAnnotationProcessor,org.springframework.context.annotation.internalAutowiredAnnotationProcessor,org.springframework.context.annotation.internalRequiredAnnotationProcessor,org.springframework.context.annotation.internalCommonAnnotationProcessor,org.springframework.context.event.internalEventListenerProcessor,org.springframework.context.event.internalEventListenerFactory,batchConfiguration]; root of factory hierarchy
08:26:18.979 [main] DEBUG o.s.b.f.s.DefaultListableBeanFactory - Creating shared instance of singleton bean 
...
08:26:32.560 [main] DEBUG o.s.b.f.s.DefaultListableBeanFactory - Returning cached instance of singleton bean 'lifecycleProcessor'
08:26:32.560 [main] DEBUG o.s.b.f.s.DefaultListableBeanFactory - Returning cached instance of singleton bean 'org.springframework.context.annotation.internalScheduledAnnotationProcessor'
08:26:32.560 [main] DEBUG o.s.b.f.s.DefaultListableBeanFactory - Returning cached instance of singleton bean 'org.springframework.boot.context.properties.ConfigurationPropertiesBindingPostProcessor'
08:26:32.560 [main] DEBUG o.s.s.a.ScheduledAnnotationBeanPostProcessor - Could not find default TaskScheduler bean
org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type [org.springframework.scheduling.TaskScheduler] is defined     at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBean(DefaultListableBeanFactory.java:372) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]      at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBean(DefaultListableBeanFactory.java:332) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
...
08:26:33.529 [pool-1-thread-1] DEBUG o.s.jdbc.core.JdbcTemplate - Executing prepared SQL update
08:26:33.529 [pool-1-thread-1] DEBUG o.s.jdbc.core.JdbcTemplate - Executing prepared SQL statement [UPDATE BATCH_JOB_EXECUTION set START_TIME = ?, END_TIME = ?,  STATUS = ?, EXIT_CODE = ?, EXIT_MESSAGE = ?, VERSION = ?, CREATE_TIME = ?, LAST_UPDATED = ? where JOB_EXECUTION_ID = ? and VERSION = ?]
08:26:33.529 [pool-1-thread-1] DEBUG o.s.jdbc.core.JdbcTemplate - SQL update affected 1 rows
08:26:33.545 [pool-1-thread-1] DEBUG o.s.j.d.DataSourceTransactionManager - Initiating transaction commit
08:26:33.545 [pool-1-thread-1] DEBUG o.s.j.d.DataSourceTransactionManager - Committing JDBC transaction on Connection [org.hsqldb.jdbc.JDBCConnection@33bbce9c]
08:26:33.545 [pool-1-thread-1] DEBUG o.s.j.d.DataSourceTransactionManager - Releasing JDBC Connection [org.hsqldb.jdbc.JDBCConnection@33bbce9c] after transaction
08:26:33.545 [pool-1-thread-1] DEBUG o.s.jdbc.datasource.DataSourceUtils - Returning JDBC Connection to DataSource
08:26:33.545 [pool-1-thread-1] INFO  o.s.b.c.l.support.SimpleJobLauncher - Job: [SimpleJob: [name=job1]] completed with the following parameters: [{}] and the following status: [COMPLETED]

2) Main method with SpringApplication.run

2) 使用 SpringApplication.run 的 Main 方法

@SpringBootApplication
public class DemoApplication {
    public static void main(String[] args) {
        SpringApplication.run(BatchConfiguration.class, args);
    }
}

Entire output:

整个输出:

: Spring Boot ::        (v1.3.1.RELEASE)
2016-02-12 08:02:36.145  INFO 12172 --- [           main] com.example.DemoApplication              : Starting DemoApplication on GH-VDIKCISV252 with PID 12172 (C:\STS\wsRestTemplate\demo\target\classes started by e049447 in C:\STS\wsRestTemplate\demo)
2016-02-12 08:02:36.145  INFO 12172 --- [           main] com.example.DemoApplication              : No active profile set, falling back to default profiles: default
2016-02-12 08:02:36.473  INFO 12172 --- [           main] s.c.a.AnnotationConfigApplicationContext : Refreshing org.springframework.context.annotation.AnnotationConfigApplicationContext@4e4aea35: startup date [Fri Feb 12 08:02:36 CST 2016]; root of context hierarchy
2016-02-12 08:02:42.176  WARN 12172 --- [           main] o.s.c.a.ConfigurationClassEnhancer       : @Bean method ScopeConfiguration.stepScope is non-static and returns an object assignable to Spring's BeanFactoryPostProcessor interface. This will result in a failure to process annotations such as @Autowired, @Resource and @PostConstruct within the method's declaring @Configuration class. Add the 'static' modifier to this method to avoid these container lifecycle issues; see @Bean javadoc for complete details.
2016-02-12 08:02:42.349  WARN 12172 --- [           main] o.s.c.a.ConfigurationClassEnhancer       : @Bean method ScopeConfiguration.jobScope is non-static and returns an object assignable to Spring's BeanFactoryPostProcessor interface. This will result in a failure to process annotations such as @Autowired, @Resource and @PostConstruct within the method's declaring @Configuration class. Add the 'static' modifier to this method to avoid these container lifecycle issues; see @Bean javadoc for complete details.
2016-02-12 08:02:42.724  INFO 12172 --- [           main] o.s.j.d.e.EmbeddedDatabaseFactory        : Starting embedded database: url='jdbc:hsqldb:mem:testdb', username='sa'
2016-02-12 08:02:43.802  WARN 12172 --- [           main] o.s.b.c.l.AbstractListenerFactoryBean    : org.springframework.batch.item.ItemReader is an interface.  The implementing class will not be queried for annotation based listener configurations.  If using @StepScope on a @Bean method, be sure to return the implementing class so listner annotations can be used.
2016-02-12 08:02:44.990  INFO 12172 --- [           main] o.s.jdbc.datasource.init.ScriptUtils     : Executing SQL script from class path resource [org/springframework/batch/core/schema-hsqldb.sql]
2016-02-12 08:02:45.179  INFO 12172 --- [           main] o.s.jdbc.datasource.init.ScriptUtils     : Executed SQL script from class path resource [org/springframework/batch/core/schema-hsqldb.sql] in 189 ms.
2016-02-12 08:02:46.804  INFO 12172 --- [           main] o.s.j.e.a.AnnotationMBeanExporter        : Registering beans for JMX exposure on startup
2016-02-12 08:02:46.868  INFO 12172 --- [           main] o.s.b.a.b.JobLauncherCommandLineRunner   : Running default command line with: []
2016-02-12 08:02:46.962  INFO 12172 --- [           main] o.s.b.c.r.s.JobRepositoryFactoryBean     : No database type set, using meta data indicating: HSQL
2016-02-12 08:02:47.040  INFO 12172 --- [pool-2-thread-1] o.s.b.c.r.s.JobRepositoryFactoryBean     : No database type set, using meta data indicating: HSQL
2016-02-12 08:02:47.243  INFO 12172 --- [           main] o.s.b.c.l.support.SimpleJobLauncher      : No TaskExecutor has been set, defaulting to synchronous executor.
2016-02-12 08:02:47.259  INFO 12172 --- [pool-2-thread-1] o.s.b.c.l.support.SimpleJobLauncher      : No TaskExecutor has been set, defaulting to synchronous executor.
2016-02-12 08:02:47.321  INFO 12172 --- [           main] o.s.b.c.l.support.SimpleJobLauncher      : Job: [SimpleJob: [name=job1]] launched with the following parameters: [{run.id=1}]
2016-02-12 08:02:47.368  INFO 12172 --- [           main] o.s.batch.core.job.SimpleStepHandler     : Executing step: [step1]
2016-02-12 08:02:47.400  INFO 12172 --- [           main] com.example.CustomItemReader             : read method - collecting the MYAPP2 out file names
2016-02-12 08:02:47.525  INFO 12172 --- [           main] com.example.CustomItemReader             : read method - no file found
2016-02-12 08:02:47.556  INFO 12172 --- [           main] o.s.b.c.l.support.SimpleJobLauncher      : Job: [SimpleJob: [name=job1]] completed with the following parameters: [{run.id=1}] and the following status: [COMPLETED]
2016-02-12 08:02:47.556  INFO 12172 --- [           main] com.example.DemoApplication              : Started DemoApplication in 12.1 seconds (JVM running for 13.405)
2016-02-12 08:02:47.556  INFO 12172 --- [pool-2-thread-1] o.s.b.c.l.support.SimpleJobLauncher      : Job: [SimpleJob: [name=job1]] launched with the following parameters: [{}]
2016-02-12 08:02:47.618  INFO 12172 --- [pool-2-thread-1] o.s.batch.core.job.SimpleStepHandler     : Executing step: [step1]
2016-02-12 08:02:47.634  INFO 12172 --- [pool-2-thread-1] com.example.CustomItemReader             : read method - collecting the MYAPP2 out file names
2016-02-12 08:02:47.634  INFO 12172 --- [pool-2-thread-1] com.example.CustomItemReader             : read method - no file found
2016-02-12 08:02:47.650  INFO 12172 --- [pool-2-thread-1] o.s.b.c.l.support.SimpleJobLauncher      : Job: [SimpleJob: [name=job1]] completed with the following parameters: [{}] and the following status: [COMPLETED]

BatchConfiguration class

BatchConfiguration 类

@Configuration
@ComponentScan("com.example")
@EnableBatchProcessing
@EnableAutoConfiguration
@EnableScheduling
@PropertySource("config.properties")
public class BatchConfiguration {
       @Autowired
       private JobBuilderFactory jobBuilderFactory;
       @Autowired
       private StepBuilderFactory stepBuilderFactory;
       @Bean
       public Step step1(ItemReader<String> reader,
                     ItemProcessor<String, String> processor, ItemWriter<String> writer) {
              return stepBuilderFactory.get("step1").<String, String> chunk(1)                          .reader(reader).processor(processor).writer(writer)
                           .allowStartIfComplete(true).build();
       }
//I took out the rest of BatchConfiguration class

Application.properties (only one line)

Application.properties(只有一行)

logging.level.*=OFF

P.S. I will not show config.properties because it only contains several property names with path settup used in business logic

PS 我不会显示 config.properties 因为它只包含几个属性名称,在业务逻辑中使用路径设置

pom.xml

pom.xml

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
       <modelVersion>4.0.0</modelVersion>
       <groupId>com.example</groupId>
       <artifactId>demo</artifactId>
       <version>0.0.1-SNAPSHOT</version>
       <packaging>jar</packaging>
       <name>demo</name>
       <description>Demo project for Spring Boot</description>
       <parent>
              <groupId>org.springframework.boot</groupId>
              <artifactId>spring-boot-starter-parent</artifactId>
              <version>1.3.1.RELEASE</version>
              <relativePath /> <!-- lookup parent from repository -->
       </parent>
       <properties>
              <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
              <java.version>1.8</java.version>
              <spring.batch.version>3.0.6.RELEASE</spring.batch.version>
       </properties>
       <dependencies>
              <dependency>
                     <groupId>org.springframework.boot</groupId>
                     <artifactId>spring-boot-starter-batch</artifactId>
              </dependency>
              <dependency>
                     <groupId>org.springframework.boot</groupId>
                     <artifactId>spring-boot-starter-test</artifactId>
                     <scope>test</scope>
              </dependency>
       </dependencies>
       <build>
              <plugins>
                     <plugin>
                           <groupId>org.springframework.boot</groupId>
                           <artifactId>spring-boot-maven-plugin</artifactId>
                     </plugin>
                     <plugin>
                           <artifactId>maven-assembly-plugin</artifactId>
                           <configuration>
                                  <archive>
                                         <manifest>
                                                <mainClass>com.example.DemoAppNoBoot</mainClass>
                                         </manifest>
                                  </archive>
                                  <descriptorRefs>
                                         <descriptorRef>jar-with-dependencies</descriptorRef>
                                  </descriptorRefs>
                           </configuration>
                           <executions>
                                  <execution>
                                         <phase>install</phase>
                                         <goals>
                                                <goal>single</goal>
                                         </goals>
                                  </execution>
                           </executions>
                     </plugin>
                     <plugin>
                           <groupId>org.apache.maven.plugins</groupId>
                           <artifactId>maven-release-plugin</artifactId>
                           <version>2.5.1</version>
                           <configuration>
                                  <goals>install</goals>
                                  <preparationGoals>install</preparationGoals>
                           </configuration>
                     </plugin>
                     <plugin>
                           <groupId>org.apache.maven.plugins</groupId>
                           <artifactId>maven-jar-plugin</artifactId>
                           <configuration>
                                  <archive>
                                         <manifest>
                                                <addClasspath>true</addClasspath>
                                                <mainClass>com.example.DemoAppNoBoot</mainClass>
                                         </manifest>
                                  </archive>
                           </configuration>
                     </plugin>
              </plugins>
       </build>
</project>

Maven Dependencies (the relevant ones for my doubt):

Maven 依赖项(与我怀疑相关的那些):

logback-classic-1.1.3.jar
logback-core-1.1.3.jar
slf4j-api-1.7.13.jar
log4j-over-slf4j-1.7.13.jar

回答by marok

In application.properties you can add ‘logging.level.*=LEVEL' where ‘LEVEL' is one of TRACE, DEBUG, INFO, WARN, ERROR, FATAL, OFF. * is responsible for package/class.

在 application.properties 中,您可以添加“logging.level.*=LEVEL”,其中“LEVEL”是 TRACE、DEBUG、INFO、WARN、ERROR、FATAL、OFF 之一。* 负责包/类。

For example

例如

logging.level.root=WARN
logging.level.org.springframework.web=DEBUG
logging.level.org.hibernate=ERROR

This means that root logger has WARN level. org.springframework.web is on DEBUG level, but all hibernates files are logged only ERROR.

这意味着根记录器具有 WARN 级别。org.springframework.web 处于调试级别,但所有休眠文件仅记录错误。

In your case you must set logging.level.root on one of level from INFO, WARN, ERROR,FATAL or OFF to turn off all logging.

在您的情况下,您必须将 logging.level.root 设置为 INFO、WARN、ERROR、FATAL 或 OFF 级别之一以关闭所有日志记录。

See https://docs.spring.io/spring-boot/docs/current/reference/html/boot-features-logging.html#boot-features-custom-log-levels

https://docs.spring.io/spring-boot/docs/current/reference/html/boot-features-logging.html#boot-features-custom-log-levels

回答by Srikanth

While using Spring Rest Docs with SpringMockMVC with testLogging.showStandardStreams set to true in Gradle, Spring cluttered the console with info & debug logs. I had to use Mkyong's solutionwhere in a logback-test.xml in src/test/resources needs to be created on top of the chosen solution here. Use log-level OFF, ERROR, WARN, DEBUG

在将 Spring Rest Docs 与 SpringMockMVC 结合使用时,在 Gradle 中将 testLogging.showStandardStreams 设置为 true 时,Spring 用信息和调试日志弄乱了控制台。我不得不使用Mkyong 的解决方案,其中 src/test/resources 中的 logback-test.xml 需要在此处选择的解决方案之上创建。使用日志级别 OFF、ERROR、WARN、DEBUG

logback-test.xml

logback-test.xml

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <include resource="org/springframework/boot/logging/logback/base.xml" />
    <logger name="org.springframework" level="ERROR"/>
</configuration>

回答by Srikanth

in addition to a log4j.properties or log4j.xml file you will need all three of these entries in your maven pom.xml... adding the log4j-acl artifact instantly fixed the problem for me. it routes apache-commons-logging entries from commons logging over to log4j

除了 log4j.properties 或 log4j.xml 文件之外,您的 maven pom.xml 中还需要所有这三个条目……添加 log4j-acl 工件立即为我解决了这个问题。它将 apache-commons-logging 条目从 commons 路由到 log4j

I'm not sure how you would go about this in grunt but the bridge is what you need.

我不确定你会如何用咕噜声来解决这个问题,但桥是你需要的。

    <!-- Log4J -->
    <dependency>
        <groupId>org.apache.logging.log4j</groupId>
        <artifactId>log4j-api</artifactId>
        <version>${log4j.version}</version>
    </dependency>
    <dependency>
        <groupId>org.apache.logging.log4j</groupId>
        <artifactId>log4j-core</artifactId>
        <version>${log4j.version}</version>
    </dependency>
    <dependency>
        <groupId>org.apache.logging.log4j</groupId>
        <artifactId>log4j-jcl</artifactId>
        <version>${log4j.version}</version>
    </dependency>