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.

Practice

1. What is the purpose of setting logging.level.<package>=<level> in Spring Boot's application.properties?

easy

A. To control the logging detail for a specific Java package

B. To define the database connection URL

C. To set the server port number

D. To configure the application's timezone

Solution

1. Step 1: Understand the configuration key

   The key logging.level.<package> is used to specify logging levels for Java packages in Spring Boot.

2. Step 2: Identify the purpose of this setting

   This setting controls how detailed the logs are for that package, helping to focus on important logs and reduce noise.

3. Final Answer:

   To control the logging detail for a specific Java package -> Option A

4. Quick Check:

   Package-level log control = A [OK]

Hint: Remember: logging.level.package sets log detail per package [OK]

Common Mistakes:

• Confusing logging level with server or database settings
• Trying to set logging level without specifying a package
• Using incorrect property keys like logging.package.level

2. Which of the following is the correct syntax to set the log level to DEBUG for the package com.example.service in application.properties?

easy

A. logging.level=com.example.service=DEBUG

B. log.level.com.example.service=DEBUG

C. logging.com.example.service.level=DEBUG

D. logging.level.com.example.service=DEBUG

Solution

1. Step 1: Recall the correct property format

   The correct format is logging.level.<package>=<level>, so the package name comes immediately after logging.level..

2. Step 2: Match the option to the format

   logging.level.com.example.service=DEBUG matches this format exactly: logging.level.com.example.service=DEBUG.

3. Final Answer:

   logging.level.com.example.service=DEBUG -> Option D

4. Quick Check:

   Correct syntax = B [OK]

Hint: Use logging.level.package=LEVEL exactly as shown [OK]

Common Mistakes:

• Adding extra '=' signs in the property
• Swapping order of package and level
• Using 'log.level' instead of 'logging.level'

3. Given the following application.properties settings:
logging.level.com.example=INFO
logging.level.com.example.service=DEBUG
What will be the log level for classes in com.example.service package?

medium

A. INFO

B. DEBUG

C. ERROR

D. WARN

Solution

1. Step 1: Understand package-level log hierarchy

   More specific package settings override broader ones. Here, com.example.service is more specific than com.example.

2. Step 2: Determine effective log level

   The com.example.service package is set to DEBUG, which overrides the INFO level set for com.example.

3. Final Answer:

   DEBUG -> Option B

4. Quick Check:

   Specific package level overrides general = C [OK]

Hint: More specific package log level overrides parent package [OK]

Common Mistakes:

• Assuming parent package level applies to all subpackages
• Ignoring more specific package settings
• Confusing INFO and DEBUG levels

4. You set logging.level.com.example=TRACE in application.properties but still see only INFO logs from com.example classes. What is the most likely cause?

medium

A. Logging is disabled globally

B. TRACE level is not supported in Spring Boot

C. Another configuration overrides the log level to INFO

D. The package name is misspelled in the properties file

Solution

1. Step 1: Verify if TRACE is supported

   TRACE is a valid log level in Spring Boot, so this is not the issue.

2. Step 2: Consider configuration overrides

   If logs show INFO instead of TRACE, likely another config (like environment variables or YAML) overrides the level to INFO.

3. Final Answer:

   Another configuration overrides the log level to INFO -> Option C

4. Quick Check:

   Config override causes unexpected log level = D [OK]

Hint: Check for conflicting configs if log level seems ignored [OK]

Common Mistakes:

• Assuming TRACE is unsupported
• Not checking for typos in package name
• Ignoring global logging settings

5. You want to reduce log noise by setting ERROR level for com.example.repository but keep DEBUG for com.example.service. Which application.properties configuration achieves this?

hard

A. logging.level.com.example.repository=ERROR
logging.level.com.example.service=DEBUG

B. logging.level.com.example=ERROR
logging.level.com.example.service=DEBUG

C. logging.level.com.example.repository=DEBUG
logging.level.com.example.service=ERROR

D. logging.level.com.example.repository=INFO
logging.level.com.example.service=DEBUG

Solution

1. Step 1: Set ERROR level specifically for repository package

   Use logging.level.com.example.repository=ERROR to reduce noise from repository logs.

2. Step 2: Set DEBUG level specifically for service package

   Use logging.level.com.example.service=DEBUG to keep detailed logs for service package.

3. Step 3: Combine both settings correctly

   logging.level.com.example.repository=ERROR logging.level.com.example.service=DEBUG correctly sets both packages with their respective levels in application.properties.

4. Final Answer:

   logging.level.com.example.repository=ERROR logging.level.com.example.service=DEBUG -> Option A

5. Quick Check:

   Separate package levels set correctly = A [OK]

Hint: Set each package level separately for precise control [OK]

Common Mistakes:

• Setting parent package level instead of specific packages
• Swapping log levels between packages
• Using incorrect property keys or syntax