-
Bug
-
Resolution: Done
-
Undefined
-
None
-
False
-
-
False
-
-
Before reporting an issue
[X] I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.
Area
core
Describe the bug
Keycloak (at least 25.0.6) does not use log-syslog-max-length configured in keycloak.conf or environment variables (console flag not tested)
Version
25.0.6
Regression
[ ] The issue is a regression
Expected behavior
Keycloak uses configured value from log-syslog-max-length
Actual behavior
Neither setting the value in keycloak.conf nor in environment variables work. It's always the mentioned default of 2048B for RFC 5424.
Other settings from keycloak.conf and environment do work.
Setting the raw quarkus property quarkus.log.syslog.max-length in quarkus.properties works.
How to Reproduce?
Start Keycloak with syslog logging enabled and send "long" messages.
Anything else?
We enabled syslog json logging to parse the logs with Graylog. With enabled json logging the log messages exceed the default 2048B very quickly. At least stack traces will exceed the default size.
- links to