PingAccess logs

The following table identifies the available PingAccess logs and their purposes.

PingAccess Logs and Purposes
Name Purpose
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.


The 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.