PingAccess

Logging, reporting, and troubleshooting

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

pingaccess.log

Primary troubleshooting log. Records PingAccess runtime and administrative server activities.

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) requests.

pingaccess_api_audit.log

Records PingAccess administrative application programming interface (API) transactions. These transactions capture activity in the PingAccess administrative console. If you’re 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_sideband_client_audit.log

Records transactions sent to and from the sideband client integration.

pingaccess_sideband_audit.log

Records the end-user transactions that the sideband client request captures.
Troubleshooting

  • The pingaccess.log file is the primary troubleshooting log.

  • Alongside an HTTP trace from the browser, which you can generate from a debugging application like Fiddler, the pingaccess_engine_audit.log and pingaccess_agent_audit.log files are helpful for identifying issues that must be resolved.

For more information about managing PingAccess logs, see Log configuration.