Repository navigation
|
We recently brought up Keycloak 26.5.0 using the following command:
Since trace is the most verbose logging level, we expected all logs to align with Keycloak’s defined log levels. However, after the server started, we noticed some log entries with the level FINE, which is not listed among the supported Keycloak log levels Below is the sample output
From the sample example, logs from the following sources appear with the FINE level are from Looking at the KeycloakLogger.java file, it seems there is a mapping intended to translate Liquibase log levels into Keycloak’s supported levels. Yet, these FINE messages are still being printed directly to the console without conversion. Question:
|
Replies: 2 comments
I'm not sure, that will take more investigation. More than likely these are output prior to the installation of the KeycloakLogService, as you can see that it's still being loaded: 2026-01-06 19:13:50,573 FINE [liquibase.servicelocator] (main) Loaded liquibase.logging.LogService instance org.keycloak.quarkus.runtime.storage.database.liquibase.KeycloakLogService As long as subsequent logging uses the Keycloak logic, then I don't think there is an issue here. |
|
Hi @shawkins , Thanks for the confirmation and answer. |
I'm not sure, that will take more investigation. More than likely these are output prior to the installation of the KeycloakLogService, as you can see that it's still being loaded:
2026-01-06 19:13:50,573 FINE [liquibase.servicelocator] (main) Loaded liquibase.logging.LogService instance org.keycloak.quarkus.runtime.storage.database.liquibase.KeycloakLogService
As long as subsequent logging uses the Keycloak logic, then I don't think there is an issue here.