If a user can simply solve this using a `ScriptFilter`, I am not keen on adding a custom filter to support this use case out of the box – in particular, when the user themselves signals "a poor design" on the application side.
I am in favor of making the custom filter implementation process as frictionless as possible, instead of making them a part of the default distribution. I think `PatternLayout` and `JsonTemplateLayout` are good examples of this principle – we stopped serving structures, but enabled users to serve themselves instead. On Thu, Apr 4, 2024 at 10:46 PM Piotr P. Karwasz <piotr.karw...@gmail.com> wrote: > Hi Ralph, > > On Thu, 4 Apr 2024 at 21:01, Ralph Goers <ralph.go...@dslextreme.com> > wrote: > > I really have no idea why but this is the first time I have heard > someone ask for the ability to filter based on the Exception class. > > This came out at least once before: see the SO "Log4j - How to log > specific exception into a separate file?" question[1]. > > There is a sample code in the answer to that question, feel free to > make a PR out of it. > > Piotr > > [1] https://stackoverflow.com/q/76919416/11748454 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-user-h...@logging.apache.org > >
