Page created: 27 Jul 2022 |
Page updated: 6 Feb 2023
This section provides a brief summary and purpose of the available logging, reporting, and troubleshooting for PingAccess.
The following table identifies the available PingAccess logs and their purposes.
|pingaccess_engine_audit.log||Records transactions of configured resources. Additionally, the log records transaction details when PingAccess sends requests to PingFederate, such as Security Token Service (STS), OAuth2, and JSON Web Signature (JWS).|
|pingaccess_api_audit.log||Records PingAccess administrative API transactions. These transactions represent activity in the PingAccess administrative console. If you are using scripts to configure PingAccess, this log also records transaction activity.|
|pingaccess_agent_audit.log||Records transactions between PingAccess Agents and the PingAccess Engine.|
|pingaccess.log||Primary troubleshooting log that records PingAccess runtime and administrative server activities.|
TroubleshootingThe pingaccess.log file represents the primary troubleshooting log. However, the pingaccess_engine_audit.log and pingaccess_agent_audit.log files are also useful. Along with an HTTP trace from the browser, which can be generated from a debugging application like Fiddler, these files are helpful for identifying issues that must be resolved.
For more information about managing PingAccess logs, see Configure logging.