SLF4J and Logback basics in Spring Boot - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is SLF4J in the context of Spring Boot?

SLF4J stands for Simple Logging Facade for Java. It acts like a simple interface or a bridge that lets your Spring Boot app use different logging tools without changing your code.

beginner

What role does Logback play when used with SLF4J?

Logback is a logging framework that actually writes the logs to files or console. SLF4J sends the logging calls to Logback, which then handles how and where the logs appear.

beginner

How do you write a simple log message using SLF4J in a Spring Boot application?

You first create a Logger object using LoggerFactory, then call methods like logger.info("message") to log info-level messages.

intermediate

What is the default logging level in Spring Boot when using Logback?

The default logging level is INFO, which means it shows informational messages, warnings, and errors but hides debug and trace messages.

intermediate

Why is it useful to separate logging interface (SLF4J) from the logging implementation (Logback)?

Separating them lets you change the logging tool (like switching from Logback to Log4j) without changing your app code. It makes your app flexible and easier to maintain.

What does SLF4J provide in a Spring Boot application?

A A simple logging interface to connect with different logging frameworks

B A database connection manager

C A web server

D A user interface library

SLF4J is a logging facade that allows your app to use different logging frameworks through a simple interface.

Which logging framework is commonly used as the default implementation with SLF4J in Spring Boot?

A Logback

B Log4j

C java.util.logging

D SLF4J itself

Spring Boot uses Logback as the default logging implementation behind SLF4J.

How do you create a logger instance in a Spring Boot class using SLF4J?

A Logger logger = Logger.getLogger();

B Logger logger = new Logger();

C Logger logger = Logback.getLogger();

D Logger logger = LoggerFactory.getLogger(ClassName.class);

You use LoggerFactory.getLogger with the class name to create a logger instance.

What logging level will show debug messages in Spring Boot by default?

A ERROR

B DEBUG

C INFO

D WARN

By default, Spring Boot uses INFO level, so debug messages are hidden unless you change the level.

Why might you want to change the logging level in a Spring Boot app?

A To speed up the app's UI

B To see more or fewer details in logs for troubleshooting

C To change the database connection

D To update the app's theme

Changing logging levels helps you control how much detail you see in logs, useful for debugging or reducing noise.

Explain how SLF4J and Logback work together in a Spring Boot application.

Think of SLF4J as the messenger and Logback as the writer.

Describe how to create and use a logger in a Spring Boot class using SLF4J.

Remember the LoggerFactory and the common log methods.

Practice

1. What is the main purpose of SLF4J in a Spring Boot application?

easy

A. To provide a simple and consistent logging interface

B. To store log files on disk

C. To send logs to a remote server

D. To format log messages with colors

Solution

1. Step 1: Understand SLF4J's role

   SLF4J acts as a simple facade or interface for various logging frameworks, allowing consistent logging calls.

2. Step 2: Differentiate from log storage

   SLF4J itself does not handle storing or formatting logs; that is done by the logging backend like Logback.

3. Final Answer:

   To provide a simple and consistent logging interface -> Option A

4. Quick Check:

   SLF4J = Simple logging interface [OK]

Hint: SLF4J is the logging interface, not the storage tool [OK]

Common Mistakes:

• Confusing SLF4J with the logging backend
• Thinking SLF4J formats or stores logs
• Assuming SLF4J sends logs remotely

2. Which of the following is the correct way to create a logger using SLF4J in a Spring Boot class?

easy

A. private Logger logger = LoggerFactory.createLogger();

B. Logger logger = new Logger();

C. private static final Logger logger = LoggerFactory.getLogger(MyClass.class);

D. Logger logger = Logger.getLogger();

Solution

1. Step 1: Recall SLF4J logger creation syntax

   The standard way is to use LoggerFactory.getLogger with the class name as parameter.

2. Step 2: Check each option

   private static final Logger logger = LoggerFactory.getLogger(MyClass.class); matches the correct syntax; others use incorrect methods or constructors.

3. Final Answer:

   private static final Logger logger = LoggerFactory.getLogger(MyClass.class); -> Option C

4. Quick Check:

   Logger creation = LoggerFactory.getLogger(Class) [OK]

Hint: Use LoggerFactory.getLogger with your class name [OK]

Common Mistakes:

• Trying to instantiate Logger with new keyword
• Using Logger.getLogger() without parameters
• Missing static or final keywords

3. Given the following code snippet in a Spring Boot app using SLF4J and Logback:

logger.info("User {} logged in", username);

What will be the output if username is "Alice"?

medium

A. User {} logged in Alice

B. User {} logged in

C. User username logged in

D. User Alice logged in

Solution

1. Step 1: Understand SLF4J placeholder usage

   The curly braces {} act as placeholders replaced by the following arguments in order.

2. Step 2: Substitute username value

   Since username is "Alice", it replaces the {} placeholder in the message.

3. Final Answer:

   User Alice logged in -> Option D

4. Quick Check:

   Placeholders {} replaced by arguments [OK]

Hint: {} placeholders get replaced by arguments in order [OK]

Common Mistakes:

• Printing the placeholder {} literally
• Printing variable name instead of value
• Appending variable after the message

4. You have this code snippet:

Logger logger = LoggerFactory.getLogger(MyClass.class);
logger.debug("Debug message");

But you never see the debug message in your console logs. What is the most likely reason?

medium

A. The logger was not created correctly

B. The log level is set higher than DEBUG in Logback configuration

C. SLF4J does not support debug messages

D. You must call logger.info() instead of logger.debug()

Solution

1. Step 1: Understand log levels and filtering

   Logback filters messages below the configured log level, so DEBUG messages may be hidden if level is INFO or higher.

2. Step 2: Check logger creation and SLF4J support

   The logger is created correctly and SLF4J supports debug messages, so those are not the cause.

3. Final Answer:

   The log level is set higher than DEBUG in Logback configuration -> Option B

4. Quick Check:

   Log level filtering hides DEBUG if set higher [OK]

Hint: Check Logback log level to see debug messages [OK]

Common Mistakes:

• Assuming logger creation failed
• Thinking SLF4J lacks debug support
• Believing debug logs always show by default

5. You want to configure Logback to write error logs to a file named errors.log and all logs to the console. Which Logback configuration snippet correctly achieves this?

hard

A.

errors.log

%d %-5level %logger{36} - %msg%n

ERROR
ACCEPT
DENY

%d %-5level %logger{36} - %msg%n

B.

errors.log

%d %-5level %logger{36} - %msg%n

%d %-5level %logger{36} - %msg%n

C.

errors.log

%d %-5level %logger{36} - %msg%n

INFO
ACCEPT
DENY

%d %-5level %logger{36} - %msg%n

D.

errors.log

%d %-5level %logger{36} - %msg%n

%d %-5level %logger{36} - %msg%n

Solution

1. Step 1: Locate the ERROR LevelFilter on FILE appender

   The FILE appender uses ch.qos.logback.classic.filter.LevelFilter with <level>ERROR</level>, <onMatch>ACCEPT</onMatch>, <onMismatch>DENY</onMismatch>. This ensures only ERROR logs go to errors.log.

2. Step 2: Confirm console appender and root logger

   The CONSOLE appender has no filter. The <root level="DEBUG"> attaches both appenders, so all logs (DEBUG and above) go to console.

3. Final Answer:

   The configuration with ERROR LevelFilter on FILE appender -> Option A

4. Quick Check:

   File appender filters ERROR, console shows all [OK]

Hint: Use LevelFilter on file appender for ERROR logs only [OK]

Common Mistakes:

• Not filtering file appender logs by level
• Setting root level too high hiding logs
• Missing console appender or not attaching it