This section explains the logging practices of PingFederate and discusses minimizing the system's overall performance impact.
Logging tracks various aspects of the system's overall performance and requires a certain amount of system resources, which affects the system's overall performance. In particular, writing to the log files takes the greatest amount of resources. To minimize the performance impact, PingFederate uses the high-performance asynchronous logger from Log4j 2 for logging runtime and administrative events, including status and error messages used for troubleshooting. To preserve transactional integrity, audit information logs synchronously.
Although the bulk of logging is executed asynchronously, decreasing the amount of information written to log files always provides the best possible performance.
PingFederate only records messages tagged with log
FATAL to the server log and the provisioner log. Messages with
TRACE tags, are not recorded to optimize
performance. Console logging is also disabled for the same reason.
DEBUGin the log4j2.xml file and re-enable console logging.
When you no longer require debug messages and console logging, turn them off. On Windows, never highlight the console output because it might slow or stop PingFederate from processing requests.