Keycloak does provide a comprehensive logging configuration capabilities based on the JBoss Logging framework as per the Server's Configuring logging guide.

However, with the Keycloak server based on Quarkus, it is currently not possible to adjust the log level dynamically, as it was possible before with the Keycloak Wildfly-based server.

To help with troubleshooting it is not acceptable from an end-user perspective to always restart the server as it would cause service interruptions.
Also the server needs to be restarted twice to reduce the logging because of resource issues as a verbose logging can cause a full filesystem and is mostly needed for a temporary period for troubleshooting.

A minimum requirement would be to have an Admin CLI for the Keycloak server in order to be able to add/update/delete, at runtime, one or many logging categories with their appropriate logging levels accordingly to the target troubleshooting requirements or needs.