Repository navigation
Replies: 4 comments 2 replies
|
If my understanding of the docs is correct, max-length with trunacte=false will split the message. I don't see another way to get that behavior other than exposing this option. @mabartos can you comment on this? |
|
@shawkins, my question was w.r.t. Keycloak not having its own native KC_* variable for QUARKUS_LOG_SYSLOG_TRUNCATE. Should we use the Quarkus environment variable itself until Keycloak adds native variable support for this option too? |
|
@Swasthik-S-Nettar
Not really. We don't usually map all Quarkus options by Keycloak options - we just go over them, and the most useful are propagated. Then, it's up to the requirements of the community what they want to use and we can provide it.
Relying on the plain Quarkus properties is not stable nor supported. You can use it only on your own risk.
It's up to the @keycloak/cloud-native team to decide it. Personally, I don't see a problem with providing it :) cc: @shawkins |
Uh oh!
There was an error while loading. Please reload this page.
Keycloak Version Used
26.6.3 (Quarkus distribution).
Question
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.We set
log-syslog-max-length=16384with truncate disabled (audit logs can be large), so today the only way to control it is the raw Quarkus property:QUARKUS_LOG_SYSLOG_TRUNCATE=falselog-syslog-truncate/KC_LOG_SYSLOG_TRUNCATEoption intentional?QUARKUS_LOG_SYSLOG_TRUNCATEsupported/stable going forward?All reactions