Server logging
When PingFederate is configured to log DEBUG messages for troubleshooting purposes, it records all runtime and administrative events that can be used for troubleshooting in the <pf_install>/pingfederate/log/server.log file, including status and error messages.
Server log information can be output to a database server.
You can correlate server log events with audit log and request log events by using a shared log attribute. Learn more in Correlating log events using attributes.
|
|
The following table describes the recorded elements. Optionally, you can configure elements by editing the log4j2.xml file as well.
| Item | Description |
|---|---|
%d |
Event date and time. |
%X{trackingid} |
The unique ID for a user session. This attribute can be enabled on the request log and audit log to correlate runtime events. Learn more in Correlating log events using attributes. |
%X{transactionid} |
The unique ID for a single sign-on (SSO) or single logout (SLO) transaction. This attribute can be enabled on the server log, request log, and audit log to correlate runtime events. Learn more in Correlating log events using attributes. |
%X{httprequestid} |
The unique ID for an HTTP request. This attribute can be enabled on the server log, request log, and audit log to correlate runtime events. Learn more in Correlating log events using attributes. |
%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.