Avoid override of log4j2.properties during upgrade


we want to edit our log4j2.properties to change the rotation of deprecation logs.
But with upgrading ES (Ubuntu - APT) we need to merge the file with a new one (if there are any changes in the new version). Its even worse when upgrading with ansible, because we dont even see that there are changes to the file and just get the log4j2.properties.dpkg-dist .

Is there any way to solve this? Like for JAVA OPTS in the systemd override file? Or can we add an additinal log4j file to override the default one?

We have the same problem with other elasitc products like kibana (kibana.yml) and dont know how to deal with it in a good way.

Any ideas? How do you handle this override hell?

Thanks and regards

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.