Get audit and debug logs
PingOne Advanced Identity Cloud provides audit and debug logs to help you manage your tenant:
-
Use audit logs to investigate user and system behavior.
-
Use debug logs to investigate any issues that can arise in production.
You can access logs through two methods:
-
Direct log access using REST API: Retrieve log events directly from the
/monitoring/logs
REST API endpoint. With this method, you access each of your tenant environments individually and use REST API filters to refine log results. Learn more in Retrieve log entries using REST API. -
External monitoring tool using log event export: Use the
/environment/telemetry/*
REST API endpoints to configure each of your tenant environments to export log events to an external monitoring tool or Security Information and Event Management (SIEM) for real-time security monitoring and error detection. This method lets you access a single external tool, such as an OpenTelemetry-compatible SIEM or Splunk, and use its interface to refine log results. Learn more in Export log events to an external monitoring tool.

Advanced Identity Cloud stores logs for 30 days.
Advanced Identity Cloud provides a console for monitoring log entries in your tenant. This beta feature is limited to development and sandbox[1] environments. Learn more in Monitor log entries in the admin console. |
Sources
Advanced Identity Cloud makes browsing the logs easier by storing them in various sources.
View sources
To view a list of the available sources, use the /monitoring/logs/sources
endpoint.
Example request:
$ curl \
--request GET 'https://<tenant-env-fqdn>/monitoring/logs/sources' \
--header 'x-api-key: <api-key>' \
--header 'x-api-secret: <api-secret>'
Example response showing available sources in a result
array:
{
"result": [
"am-access", (1)
"am-activity",
"am-authentication",
"am-config",
"am-core",
"am-everything",
"idm-access", (2)
"idm-activity",
"idm-authentication",
"idm-config",
"idm-core",
"idm-everything",
"idm-recon",
"idm-sync",
"ws-activity", (3)
"ws-config",
"ws-core",
"ws-everything"
],
"resultCount": 18,
"pagedResultsCookie": null,
"totalPagedResultsPolicy": "NONE",
"totalPagedResults": 1,
"remainingPagedResults": 0
}
1 | Start of log sources for AM audit events. Learn more in AM source descriptions. |
2 | Start of log sources for IDM audit events. Learn more in IDM source descriptions. |
3 | Start of log sources for WS-Federation[2] audit events. Learn more in WS-Federation source descriptions. |
AM source descriptions
Source | Type | Description |
---|---|---|
am-access |
Audit |
Captures all incoming Advanced Identity Cloud access calls as audit events. This includes who, what, when, and the output for every access request. Audit events:
Show example
Access log format
|
am-activity |
Audit |
Captures state changes to objects that were created, updated, or deleted by Advanced Identity Cloud end users. This includes session, user profile, and device profile changes. Audit events:
Show example
Activity log format
|
am-authentication |
Audit |
Captures when and how a user authenticated and related audit events. Advanced Identity Cloud records an authentication audit event for each authentication node and the journey outcome. A node can provide extra data in the standard audit event, which is logged when an authentication node completes. Audit events:
Learn more about Authentication log format
|
am-config |
Audit |
Captures access management configuration changes for Advanced Identity Cloud with a timestamp and by whom. Configuration changes can only be performed in development environments, so these logs are empty in staging and production environments. Audit events:
Show example
Config log format
|
am-core |
Debug |
Captures access management debug logs for Advanced Identity Cloud. Use am-core when debugging anything in access management without capturing audit events. am-core also captures logging in authentication scripts. Development and sandbox environments provide DEBUG level logs, with logs in several areas tuned to INFO or WARNING. To reduce log volumes, staging and production environments only provide WARNING level logs and above. To troubleshoot and view the latest entries in the stored logs, you can tail am-core source. Learn more in Tail logs. |
am-everything |
Audit, Debug |
Captures all access management audit and debug logs for Advanced Identity Cloud. This includes all the logs captured in |
IDM source descriptions
Source | Type | Description |
---|---|---|
idm-access |
Audit |
Captures messages for the identity management REST endpoints and the invocation of scheduled tasks. This is the who, what, and output for every identity management access request in Advanced Identity Cloud. Audit events:
Show example
Learn more about |
idm-activity |
Audit |
Captures operations on internal (managed) and external (system) objects in Advanced Identity Cloud. idm-activity logs the changes to identity content, such as adding or updating users and changing passwords. Audit events:
Show example
Learn more about |
idm-authentication |
Audit |
Captures the results when authenticating to an If an authentication session already exists in access management, authentication to identity management is not required. In this instance, the authentication logs would appear for am-authentication, with identity management logs in idm-access and idm-activity. Audit events:
Learn more about |
idm-config |
Audit |
Captures identity management configuration changes for Advanced Identity Cloud with a timestamp and by whom. Configuration changes can only be performed in development environments, so these logs are empty in staging and production environments. Audit events:
Show example
Learn more about |
idm-core |
Debug |
Captures identity management debug logs for Advanced Identity Cloud. Use idm-core when debugging anything in identity management without capturing audit events. Development and sandbox environments provide FINE level logs, with logs in several areas tuned to INFO, WARNING and SEVERE. To reduce log volumes, staging and production environments only provide INFO and WARNING level logs and above. To troubleshoot and view the latest entries in the stored logs, you can tail idm-core source. Learn more in Tail logs. |
idm-everything |
Audit, Debug |
Captures identity management audit and debug logs for Advanced Identity Cloud. This includes all the logs captured in |
idm-recon |
Audit |
Captures reconciliation events for Advanced Identity Cloud. The corresponding audit topic for idm-recon is disabled by default in Advanced Identity Cloud. For reconciliation events to appear in the audit logs, you must enable the recon event handler. Learn more about |
idm-sync |
Audit |
Captures any changes to an object resulting in automatic sync (live sync and implicit sync) when a repository is mapped to Advanced Identity Cloud. This includes situations and the actions taken on each object, by account. The idm-activity log contains additional details about each action. Learn more about |
WS-Federation source descriptions
The following log sources are available for WS-Federation[2]:
Source | Type | Description |
---|---|---|
ws-activity |
Audit |
Captures WS-Federation user authentication events. Show example
Activity log format
|
ws-config |
Audit |
Captures WS-Federation configuration change events. Show example
Configuration log format
|
ws-core |
Debug |
Captures WS-Federation error and debug events. Show example
Core log format
|
ws-everything |
Audit, Debug |
Captures WS-Federation audit and debug logs for Advanced Identity Cloud. This includes all the logs captured in |