File-based logging in Spring Boot - Step-by-Step Execution

Concept Flow - File-based logging

Application starts

↓

Logging framework initializes

↓

Log event occurs

↓

Check log level

Yes No↓

Format log message

↓

Write message to log file

↓

Log file updated

↓

Application continues

This flow shows how a Spring Boot app writes logs to a file: it starts, initializes logging, checks if the log level allows writing, formats the message, writes it to the file, then continues.

Execution Sample

Spring Boot

logging.level.root=INFO
logging.file.name=app.log

logger.info("App started")

This config sets log level to INFO and writes logs to 'app.log'. The code logs an info message 'App started'.

Execution Table

Step	Action	Log Level Check	Message Formatted	File Write	File Content
1	Application starts	-	-	-
2	Logging framework initializes	-	-	-
3	Log event: logger.info("App started")	INFO >= INFO (Yes)	"INFO: App started"	Write to app.log	INFO: App started
4	Application continues	-	-	-	INFO: App started

💡 No more log events, application continues running

Variable Tracker

Variable	Start	After Step 3	Final
logLevel	INFO (configured)	INFO	INFO
logMessage	null	"App started"	"App started"
logFileContent	""	"INFO: App started\n"	"INFO: App started\n"

Key Moments - 2 Insights

Why does the log message get written to the file at step 3?

Because the log level of the message (INFO) matches or exceeds the configured root log level (INFO), so the message passes the level check and is written to the file as shown in execution_table row 3.

What happens if the log level was set to WARN instead of INFO?

If the root log level was WARN, the INFO message would fail the log level check and would not be written to the file. This would be reflected by 'No' in the 'Log Level Check' column and no change in 'File Content'.

Visual Quiz - 3 Questions

Look at the execution table, what is the content of the log file after step 3?

A "INFO: App started\n"

B "App started"

C "ERROR: App started\n"

D ""

💡 Hint

Check the 'File Content' column in row 3 of the execution_table.

At which step does the logging framework check if the log level allows writing?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at the 'Log Level Check' column in the execution_table.

If the log level was set to WARN, how would the 'File Write' column change at step 3?

A "Write to app.log"

B "Skip writing"

C "Write ERROR to app.log"

D "Write INFO to console only"

💡 Hint

Refer to key_moments explanation about log level filtering.

Concept Snapshot

File-based logging in Spring Boot:
- Configure log level with 'logging.level.root=LEVEL'
- Set log file with 'logging.file.name=filename.log'
- Logs at or above level are formatted and written to file
- Lower level logs are ignored
- Log file appends messages as app runs

Full Transcript

This visual execution shows how Spring Boot writes logs to a file. When the application starts, the logging framework initializes. When a log event occurs, it checks if the message's log level meets or exceeds the configured root log level. If yes, it formats the message and writes it to the log file. The file content updates with the new message. If the log level is lower than configured, the message is skipped. This process repeats for each log event while the application runs.