graylog.conf and log4j2.xml currently get copied from graylog2/graylog-docker, which can result in a config that's out of sync with what's expected for a given release.
Suggestions:
Stop copying graylog.conf and use the release artifact's graylog.conf.example as the basis for the image's graylog.conf
Stop copying log4j2.xml
Currently, the only difference between the graylog-docker version and graylog2-server/src/main/resources/log4j2.xml is that the former is missing a line introduced in March 2021 (<Logger name="org.apache.kafka.clients.producer.ProducerConfig" level="warn"/>).
graylog.confandlog4j2.xmlcurrently get copied from graylog2/graylog-docker, which can result in a config that's out of sync with what's expected for a given release.Suggestions:
graylog.confand use the release artifact'sgraylog.conf.exampleas the basis for the image'sgraylog.conflog4j2.xmlgraylog-dockerversion andgraylog2-server/src/main/resources/log4j2.xmlis that the former is missing a line introduced in March 2021 (<Logger name="org.apache.kafka.clients.producer.ProducerConfig" level="warn"/>).