Right now, AFAIK there is a fixed log4j configuration which is shared across all topologies in a cluster. This is currently encoded in worker.xml. I was wondering if we can have a way to override this configuration per topology
Pros > I could have a custom retention policy for each of my topology. Some applications may need a size based and file count based retention. Others may need time based retention > I could filter out the logs of a particular package into separate log file. It may not be possible to do so in the cluster wide log configuration Many more customizations are possible of course. Cons > Log management and retention could become a problem for the cluster admin. > There are security implications and permissions on log directories need to be correct. Thoughts/comments? -- Regards, Abhishek Agarwal
