SLF4J and Logback basics in Spring Boot - Step-by-Step Execution

Concept Flow - SLF4J and Logback basics

Start Application

↓

Create Logger Instance

↓

Call Logger Method (e.g., info)

↓

SLF4J Formats Message

↓

Logback Receives Log Event

↓

Logback Applies Configuration

↓

Log Message Written to Output (Console/File)

↓

End

This flow shows how a Spring Boot app uses SLF4J to send log messages that Logback formats and writes to console or files.

Execution Sample

Spring Boot

import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

Logger logger = LoggerFactory.getLogger(MyClass.class);
int userCount = 5;
logger.info("App started with {} users", userCount);

This code creates a logger and logs an info message with a dynamic user count.

Execution Table

Step	Action	Input/Method	Output/Result
1	Create Logger	LoggerFactory.getLogger(MyClass.class)	Logger instance for MyClass created
2	Call Logger Method	logger.info("App started with {} users", userCount=5)	SLF4J formats message: "App started with 5 users"
3	Send to Logback	Formatted message	Logback receives log event
4	Apply Config	Logback config (e.g., console appender, pattern)	Message formatted with timestamp and level
5	Write Output	Formatted log message	Message printed to console or written to file
6	End	No further logs	Logging cycle complete

💡 No more log calls, application continues running

Variable Tracker

Variable	Start	After Step 2	After Step 5
logger	null	Logger instance created	Logger instance reused for logging
userCount	5	5	5
formattedMessage	null	"App started with 5 users"	"App started with 5 users"

Key Moments - 3 Insights

Why do we use LoggerFactory.getLogger instead of creating Logger directly?

LoggerFactory.getLogger creates a logger tied to the class name, ensuring consistent naming and integration with SLF4J and Logback, as shown in step 1 of the execution_table.

How does SLF4J handle the message with placeholders like {}?

SLF4J replaces {} with provided arguments before sending the formatted message to Logback, as seen in step 2 where the message becomes "App started with 5 users".

What decides where the log message goes (console or file)?

Logback configuration controls output destinations and formats, applied in step 4, so changing config changes where logs appear.

Visual Quiz - 3 Questions

Look at the execution_table, what is the output after step 2?

A Message printed to console

B Logger instance created

C "App started with 5 users" formatted message

D Logback config applied

💡 Hint

Check the 'Output/Result' column for step 2 in the execution_table

At which step does Logback apply its configuration to the log message?

A Step 4

B Step 3

C Step 1

D Step 5

💡 Hint

Look for 'Apply Config' action in the execution_table

If userCount changes to 10, how does the formattedMessage change at step 2?

A "App started with 5 users"

B "App started with 10 users"

C "App started with {} users"

D No change, message stays the same

💡 Hint

Refer to variable_tracker for formattedMessage changes after step 2

Concept Snapshot

SLF4J is a logging interface used in Spring Boot.
Use LoggerFactory.getLogger(Class) to create a logger.
Call logger methods like info(), debug() with messages.
Use {} placeholders for dynamic values.
Logback is the default logger implementation.
It formats and writes logs based on config (console/file).

Full Transcript

In Spring Boot, SLF4J provides a simple way to log messages. You create a logger using LoggerFactory.getLogger with your class. When you call logger.info or other methods with a message and placeholders, SLF4J formats the message by replacing placeholders with actual values. Then, Logback receives this formatted message. Logback applies its configuration, which decides how the message looks and where it goes, like console or file. Finally, the message is output. This process repeats for each log call. Understanding this flow helps you control logging in your app.

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