Logging, reporting, and troubleshooting
This section provides an overview of the available logging, reporting, and troubleshooting features for PingFederate.
PingFederate Logs
The server.log file represents the primary troubleshooting log. Along with an HTTP trace from the browser, which can be generated from a debugging application like Fiddler, this file is helpful for identifying issues that must be resolved. The following table identifies the available PingFederate logs and summarizes their purposes.
| Name | Purpose |
|---|---|
|
Records the actions that users of the Administrative Console and the Administrative API perform. |
|
If detailed event logging is enabled, this log records detailed information about each applicable administrative event that users perform using the Administrative Console and the Administrative API. |
|
Records the actions that users of the administrative API perform. |
|
Records the actions that API users perform by using the OAuth Client Management Service, the OAuth Access Grant Management Service, and the Session Revocation API. |
|
Records individual identity-federation runtime transactions at specified levels of detail. |
|
Records a selected, configurable subset of transaction log information plus additional details. Intended for security-audit and regulatory-compliance purposes. |
|
Records outbound provisioning events intended for security-audit purposes. |
|
Records provisioning activity only. Useful when troubleshooting issues that relate to provisioning. |
|
Records PingFederate runtime and administrative server activities. For more information about the primary troubleshooting log, see Creating an error-only server log. |
|
Records only Jetty messages that are generated prior to starting PingFederate. |
|
Contains log messages and stack traces of all threads in PingFederate’s Java Virtual Machine (JVM), including Java threads and VM internal threads. This information can help with troubleshooting the root cause of potential thread exhaustion events. The format of the thread dumps can be consumed by utilities such as jstack that is included with a Java Development Kit (JDK). This log is written only if you enable the runtime notification for thread pool exhaustion events. For more information, see Configuring runtime notifications. |