--- title: Logging, reporting, and troubleshooting description: This section provides a brief summary and purpose of the available logging, reporting, and troubleshooting for PingAccess. component: pingaccess version: 9.0 page_id: pingaccess:pingaccess_monitoring_guide:pa_logging_reporting_and_troubleshooting canonical_url: https://docs.pingidentity.com/pingaccess/9.0/pingaccess_monitoring_guide/pa_logging_reporting_and_troubleshooting.html revdate: January 12, 2024 --- # 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. > **Collapse: 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) *(tooltip: \
\

An entity responsible for responding to WS-Trust requests for validation and issuance of security tokens used for SSO authentication to web services.\

\
)*, OAuth2, and JSON Web Signature (JWS) *(tooltip: \
\

A signed instance of a JSON Web Token (JWT) based on IETF standard syntax and used for the exchange of signed content.\

\
)* requests. | > | `pingaccess_api_audit.log` | Records PingAccess administrative application programming interface (API) *(tooltip: \
\

A specification of interactions available for building software to access an application or service.\

\
)* 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. | > **Collapse: 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](../configuring_and_customizing_pingaccess/pa_logging_configuration.html).