Customizing log4j2 configuration

The application uses the log4j2 (2.17.1) utility for logging. The log4j2 utility writes trace and debug information to a log file. You can modify the logging parameters in the log4j2 configuration file to control the location and level of the log files.

You can configure the logger to send different categories of messages to different destinations. Categories are organized hierarchically, which permits inheritance. Each category can be configured with a priority to indicate a severity level. If a category is not configured with a priority, it inherits the priority of its closest ancestor with an assigned priority.

You cannot customize the log4j2 configuration file. If you have any customizations by using differential extensibility or override extensibility for log4j before the 22.1 minor update 1 release, these customizations continue to work. However, if you want to add a package for which you want the login support, you must configure the following property:

yfs.log4j2.customPackages=<a comma-separated list of package names>

By default, level for the loggers are defined as VERBOSE for all packages that are provided in the yfs.log4j2.customPackages=<a comma-separated list of package names> property. If you want to define a different level for a package or packages, you must define the level for each such package in the following property:

yfs.log4j2.customPackage.<packagename>.level=<logging level for the logger>

Next-generation platform Do not change any existing appender elements. Changes to appender elements might stop the log collection process, prevent you from exporting logs in the Self Service, and prevent you from viewing log files in Graylog. Do not add appender elements. The system collects log files from the default appender elements.