Log formatting configuration in Spring Boot - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

Understanding log pattern output in Spring Boot

Given this log pattern configuration in Spring Boot:

logging.pattern.console=%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n

What will be the output format of a log entry?

A Time in hours, minutes, seconds, milliseconds, thread name in brackets, log level left-padded to 5 chars, logger name truncated to 36 chars, message, newline

B Date in yyyy-MM-dd format, thread name in brackets, log level right-padded to 5 chars, full logger name, message, newline

C Timestamp in milliseconds, thread name without brackets, log level uppercase, logger name full, message, newline

D Time in HH:mm:ss format, thread id in brackets, log level left-padded to 5 chars, logger name truncated to 20 chars, message, newline

💡 Hint

Look carefully at the pattern symbols: %d{HH:mm:ss.SSS}, [%thread], %-5level, %logger{36}, %msg%n

The pattern specifies time with hours, minutes, seconds, milliseconds (%d{HH:mm:ss.SSS}), thread name in brackets ([%thread]), left-aligned log level with width 5 (%-5level), logger name truncated to 36 characters (%logger{36}), message (%msg), and newline (%n).

📝 Syntax

intermediate

Identify the invalid log pattern syntax

Which of the following Spring Boot log pattern configurations will cause a syntax error or fail to format logs correctly?

A logging.pattern.console=%d{HH:mm:ss.SSS [%thread] %-5level %logger{36} - %msg%n

B logging.pattern.console=%d{HH:mm:ss} [%thread] %-5level %logger{20} - %msg%n

C logging.pattern.console=%d{HH:mm:ss.SSS} [%thread] %level %logger{36} - %msg%n

D logging.pattern.console=%d{HH:mm:ss.SSS} [%thread] %-5level %logger - %msg%n

💡 Hint

Check for missing or misplaced braces and brackets in the pattern.

Option A is missing the closing brace '}' after the date pattern %d{HH:mm:ss.SSS}, causing a syntax error in the log pattern.

❓ state_output

advanced

Effect of changing log pattern on output

If you change the Spring Boot log pattern from:

%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n

to:

%d{yyyy-MM-dd HH:mm:ss} [%thread] %-5level %logger{10} - %msg%n

What is the main visible difference in the log output?

A The message will be omitted from the output, showing only metadata.

B The timestamp will show only time with milliseconds, and the logger name will be fully displayed.

C The timestamp will include the full date and time, and the logger name will be truncated to 10 characters instead of 36.

D The thread name will be removed from the output, and the log level will be right-padded.

💡 Hint

Compare the date format and logger name length in both patterns.

The new pattern changes the date format to include year, month, and day, and shortens the logger name to 10 characters, affecting the visible output accordingly.

🔧 Debug

advanced

Diagnose missing thread name in logs

You configured your Spring Boot log pattern as:

logging.pattern.console=%d{HH:mm:ss.SSS} %thread %-5level %logger{36} - %msg%n

But the logs do not show the thread name in brackets as expected. What is the cause?

A The %thread placeholder is invalid and should be %t instead.

B The logger name truncation %logger{36} removes the thread name from output.

C The log level placeholder %-5level must come before the thread name to show it correctly.

D The pattern is missing brackets around %thread, so thread name appears without brackets.

💡 Hint

Look at how the thread name is enclosed in the pattern.

The pattern lacks brackets [] around %thread, so the thread name is printed plainly without brackets.

🧠 Conceptual

expert

Understanding log pattern placeholders and their effects

Which of the following statements about Spring Boot log pattern placeholders is TRUE?

A %level outputs the log level in uppercase by default.

B %msg outputs the log message without a newline character.

C %logger{length} truncates the logger name to the specified number of characters from the end.

D %thread outputs the thread ID number instead of the thread name.

💡 Hint

Recall what each placeholder outputs exactly.

Option B is true: %msg outputs the log message exactly as is, without adding a newline. The newline must be added explicitly with %n. Option B is false because %logger{length} truncates from the beginning, not the end. Option B is false because %level outputs the level in uppercase or lowercase depending on configuration but usually uppercase. Option B is false because %thread outputs the thread name, not the ID.