| Hi, trying to keep reasons on PR#266 short, in our case, now 200+ applications don't define appenders; instead they all import an external xml config file which defines an appender that is reused throuhought all applications. In the cases where we need to change the implementation of the "corporate" appender we add another reference to this appender, so applications send their logging events to both old and new appenders, transparently. When we're happy with the performance/configuration of the new appender, we remove the old one. Being able to group appenders allows to make this kind of changes transparently. This is similar to how we approach changes f.ex on databases. Luckily these kind of changes take place infrequently, but when they happen, they don't affect applications' logging configuration, thus, saving us a lot of deploys. Also, we had situations were we wanted to have logging events from several loggers sent to more than one appender, and this just saves some lines on logback.xml. Last, LOGBACK-841 seems to reference another situation were this kind of appender would come up handy. We're now working with the appender from the PR, but it would be nice to have it on logback. We see more value for it here than keeping it in-house. HTH |
