Package-level log configuration in Spring Boot - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is package-level log configuration in Spring Boot?

It is setting the logging level (like INFO, DEBUG, ERROR) specifically for a Java package or namespace to control how much log detail is shown for that part of the application.

beginner

How do you set a DEBUG log level for a package in Spring Boot's application.properties?

Add a line like logging.level.com.example.myapp=DEBUG where com.example.myapp is the package name.

intermediate

What is the effect of setting logging.level.root=ERROR in Spring Boot?

It sets the default log level for all packages to ERROR, so only error messages show unless overridden by package-level settings.

intermediate

Where can you configure package-level logging in Spring Boot besides application.properties?

You can also configure it in application.yml or programmatically using a logging framework like Logback or Log4j2 configuration files.

beginner

Why is package-level log configuration useful in a Spring Boot app?

It helps focus on logs from specific parts of the app, making debugging easier without flooding logs with too much info from other packages.

How do you set the log level for a specific package in Spring Boot using application.properties?

A logging.level.<package>=LEVEL

B log.package.<package>=LEVEL

C logging.package.<package>=LEVEL

D log.level.<package>=LEVEL

The correct syntax is logging.level.=LEVEL, for example logging.level.com.example=DEBUG.

What happens if you set logging.level.root=ERROR in Spring Boot?

A No logs will be shown

B Only ERROR and higher logs show for all packages by default

C All logs including DEBUG show for all packages

D Only INFO logs show for all packages

Setting logging.level.root=ERROR means only error and more severe logs appear by default.

Which file can you NOT use to configure package-level logging in Spring Boot?

A pom.xml

B application.yml

C logback-spring.xml

D application.properties

pom.xml is for project dependencies, not logging configuration.

Why might you want to set DEBUG level only for one package?

A To hide errors from that package

B To disable logging for that package

C To make the app run faster

D To get detailed logs only from that package without cluttering logs from others

Setting DEBUG for one package helps focus on detailed logs there without too much noise.

What is the default log level if none is set in Spring Boot?

A ERROR

B DEBUG

C INFO

D WARN

Spring Boot defaults to INFO level logging if no level is set.

Explain how to configure logging levels for specific packages in a Spring Boot application.

Think about how you control log detail for parts of your app.

Why is package-level log configuration helpful when debugging a Spring Boot app?

Imagine trying to find a problem in one part of a big app.