We have been dealing with various connection related issues between our MariaDB server and MariaDB JDBC driver usage. Most of it comes down to issues that we cannot reproduce locally and are only reproducible in production. Such issues usually require enabling DEBUG logging of MariaDB JDBC driver and then trying to correlate those logs with the server side logs. One such recent case was while investigating https://jira.mariadb.org/browse/CONJ-896. For the most part, the DEBUG logs in the JDBC driver generate good and precise information. However, there are certain log message which are missing the server thread id (the connection id) which makes it very difficult (in a busy production environment) to correlate some of these log messages with the server side logs. Having the connection id be printed in the JDBC driver log messages will go a long way in helping debug issues since this same connection id gets printed in the MariaDB server side logs, thus making it easy to correlate the log and actions that lead to those logs.