When PingFederate is configured to log DEBUG messages (for troubleshooting purpose), it records all runtime and administrative events, including status and error messages that can be used for troubleshooting, in the <pf_install>/pingfederate/log/server.log file. Server log information may be output to a database server.


DEBUG messages are turned off by default. For troubleshooting purpose, you may re-enable it by editing the <pf_install>/pingfederate/server/default/conf/log4j2.xml file.

The following table describes the recorded elements. As needed, elements are configurable by editing the log4j2.xml file as well.

Item Description
%d Event date and time.
%X{trackingid} The tracking ID values uniquely identify user sessions, useful for correlating log messages in the audit and server logs.
%p Logging level.
%c The Java class issuing the status or error message, when applicable.
%m Status or error message.

To facilitate troubleshooting, administrators can use a filter utility to aggregate related events using the log filter tool.