Details
-
Task
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
-
False
-
False
Description
Learned about this replacement for log4j 1.x: https://github.com/jboss-logging/log4j-jboss-logmanager
It is API compatible with log4j 1.x, so Kafka and Kafka Connect should be usable with it. What I don't know though is whether it's "configuration-compatible", or whether the configuration format differs.
Assuming the configuration format is different indeed, we could do the following:
- Add both the existing log4j 1.x and log4j-jboss-logmanager as files to the container images for Kafka and Kafka Connect
- Add one or the other to the Kafka libs directory, based on some environment variable e.g. as a hard-link (similar to what we do for the scripting SMTs)
- Default to using the replacement as it's the current, actively maintained option; allow to use the legacy log4j 1.x for those users who prefer it