Affects Version/s: None
Fix Version/s: 2.11.0
When using a composite logger with DefaultMergeStrategy, logger filters aren't combined properly.
Specifically, if the 'parent' configuration for the logger has no filter and the child configuration does, all attributes and children of the child filter are dropped from the composite configuration.
For example, if my parent logger has:
and the child logger has:
DefaultMergeStrategy creates a RegexFilter node in the composite configuration with no attributes. You end up getting a message like this when the RegexFilter is constructed:
A new copy of the filter node is created, but the children and attributes aren't added to the new nodes.
If the parent logger config does have a filter, it looks like it works correctly.