How to Change the Log Level of org.hibernate.SQL to INFO from DEBUG in Spring Boot

A step-by-step guide on changing the Hibernate SQL logging level in Spring Boot from DEBUG to INFO, helping developers manage logging output effectively.
---

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---

Understanding the Log Levels

Before we dive deep into changing the log level, it’s essential to understand what log levels mean in the context of logging frameworks:

DEBUG: This level provides detailed information primarily used for debugging. This can include SQL queries, variable states, and being verbose about the application’s internal workings.

INFO: The info level conveys general information about the application's operation without the comprehensive detail of debug logs. It's useful for high-level insights into what the application is doing.

The Current Situation

[[See Video to Reveal this Text or Code Snippet]]

This will output detailed SQL queries, such as:

[[See Video to Reveal this Text or Code Snippet]]

However, you may want to change the verbosity to INFO to enhance clarity and reduce clutter in your logs:

[[See Video to Reveal this Text or Code Snippet]]

The expectation is that the logs would then show an output like:

[[See Video to Reveal this Text or Code Snippet]]

But, as you've discovered, changing to INFO might not provide the results you were hoping for.

Why Can't You Change the Log Level?

The core issue lies in how Hibernate handles logging. Here’s what you need to know:

Log Statements Defined by Code: The application’s code base determines the log level at which log statements are captured. If the log statement in the Hibernate library is defined to log at the DEBUG level, changing it to INFO in your configuration won't affect the output from that part of the code.

Recommended Approaches

While you cannot directly change the log level of Hibernate SQL logs from DEBUG to INFO, you can manage different strategies to filter or handle logs effectively:

1. Adjusting Your Logging Configuration

Use a Custom Logging Filter: Consider using a logging framework, like Logback or Log4j, that allows for more sophisticated log filtering.

Review Other Loggers: Examine whether other relevant loggers are being set at the desired log levels to help you deduce SQL-related issues without needing as many log outputs.

2. Customizing Hibernate Logging

Create Custom Logging Logic: If necessary, you could capture SQL queries and log them using your logic, perhaps pushing messages to various logging levels based on criteria you set.

3. Monitoring SQL Output

For production environments, consider using tools for SQL query monitoring that might be more efficient than logging every query, such as a separate database profiler.

Conclusion

Thank you for following along, and happy coding! Remember, effective log management can greatly enhance your development workflow.