[LOG4J2-589] Allow filtering on custom levels in configuration

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-rc1
• Fix Version/s: 2.1
• Component/s: Configurators
• Labels: configuration custom level
• Assignee: Remko Popma
• Reporter: James Hutton
• Created: 31/Mar/14 12:13
• Updated: 27/Sep/14 11:59
• Resolved: 27/Sep/14 11:59

Description

Previous title: Use forName instead of getLevel and valueOf for configuration

Without this one cannot use custom log levels in configuration without forking a large amount of code. Either the forName method needs to be removed and custom log levels should be explicitly forbidden, or support should be consistent.
Classes that would need to be modified:
BaseConfiguration, NullConfiguration, and DefaultConfiguration.