log4j log4j logs customization Configuration file

Example

Configuration

Log4j configuration file can be in any of these formats:

• JSON
• YAML
• properties (text file)
• XML

Configuration discovery

1. Log4j will inspect the log4j.configurationFile system property and, if set, will attempt to load the configuration.
2. If no system property is set log4j will look for log4j2-test.properties in the classpath.
3. If no such file is found the log4j will look for log4j2-test.yaml or log4j2-test.yml in the classpath.
4. If no such file is found the log4j will look for log4j2-test.json or log4j2-test.jsn in the classpath.
5. If no such file is found the logj4 will look for log4j2-test.xml in the classpath.
6. If a test file cannot be located the log4j will look for log4j2.properties on the classpath.
7. If a properties file cannot be located the log4j will look for log4j2.yaml or log4j2.yml on the classpath.
8. If a YAML file cannot be located the log4j will look for log4j2.json or log4j2.jsn on the classpath.
9. If a JSON file cannot be located the log4j will try to locate log4j2.xml on the classpath.
10. If no configuration file could be located the DefaultConfiguration will be used. This will cause logging output to go to the console.