Description
Keycloak exposes native KC_LOG_SYSLOG_* options for almost every syslog setting (endpoint, protocol, level, max-length, async, async-queue-length, ...), but I can't find one for the Quarkus truncate behaviourQUARKUS_LOG_SYSLOG_TRUNCATE
Would you consider exposing a native KC_LOG_SYSLOG_TRUNCATE option as well?
Value Proposition
This would improve consistency across the syslog configuration. all syslog-related settings through the Keycloak configuration model without needing to fall back to Quarkus-specific properties
Goals
Follow the existing KC_LOG_SYSLOG_* naming convention.
Use the same default value as the underlying Quarkus property.
Be available through all supported Keycloak configuration mechanisms (CLI, environment variables, configuration file).
Non-Goals
Enhancement should not bring in any regression.
KC_LOG_SYSLOG_* takes precedence over Quarkus property
Discussion
#50024
Notes
No response
Description
Keycloak exposes native KC_LOG_SYSLOG_* options for almost every syslog setting (endpoint, protocol, level, max-length, async, async-queue-length, ...), but I can't find one for the Quarkus truncate behaviour
QUARKUS_LOG_SYSLOG_TRUNCATEWould you consider exposing a native
KC_LOG_SYSLOG_TRUNCATEoption as well?Value Proposition
This would improve consistency across the syslog configuration. all syslog-related settings through the Keycloak configuration model without needing to fall back to Quarkus-specific properties
Goals
Follow the existing KC_LOG_SYSLOG_* naming convention.
Use the same default value as the underlying Quarkus property.
Be available through all supported Keycloak configuration mechanisms (CLI, environment variables, configuration file).
Non-Goals
Enhancement should not bring in any regression.
KC_LOG_SYSLOG_* takes precedence over Quarkus property
Discussion
#50024
Notes
No response