Choosing the right logging configuration can make the difference between finding a performance issue during development or suffering from it on production. But it can also create an overhead that slows down your application. You need to decide which information you need and configure your system accordingly. I, therefore, prefer to use two different configurations: 1. The development configuration needs to log enough internal information to understand the database interactions, see the number of executed queries, and check the SQL statements. 2. The production configuration should avoid any overhead by logging as few messages as possible. And in addition to the target system, your configuration also depends on the Hibernate version you’re using. That’s especially the case for your development configuration. Some logging features, like the slow query log, aren’t available in older Hibernate versions, and Hibernate 6 changed the names of a few important logging categories. Because of that, I will explain the different log categories and provide you with my recommended logging configurations for development and production when using Hibernate 4, 5, and 6. Like my channel? Subscribe! ➜ http://bit.ly/2cUsid8 Read the accompanying post: https://thorben-janssen.com/hibernate-logging-guide/ Want to connect with me? Blog: https://thorben-janssen.com/ Twitter: https://twitter.com/thjanssen123 Facebook: https://www.facebook.com/thorbenjanssenofficial Linkedin: https://www.linkedin.com/in/thorbenjanssen/