---
title: PingOne Platform logging and reporting
description: PingOne includes various auditing and reporting tools for admins to monitor events in their PingOne environments.
component: pingone
page_id: pingone:getting_started_with_pingone:p1_logging_reporting_overview
canonical_url: https://docs.pingidentity.com/pingone/getting_started_with_pingone/p1_logging_reporting_overview.html
revdate: April 23, 2025
section_ids:
  audit: Audit
  webhooks: Webhooks
  pingone-api: PingOne API
  pingone-app-for-splunk: PingOne App for Splunk
  dashboards: Dashboards
  alerts: Alerts
---

# PingOne Platform logging and reporting

PingOne includes various auditing and reporting tools for admins to monitor events in their PingOne environments.

Use the information in this section to understand the various types of logs and reporting, and options for collecting and accessing log data.

You can retrieve logs through the **Audit** page, by using webhooks, or through the API. You can also use the **Dashboards** page, the **Alerts** page, and the PingOne App for Splunk to monitor your PingOne environment.

## Audit

Use the **Audit** page in the PingOne admin console to run queries on events and actions in the PingOne environment. PingOne auditing functionality captures two types of data that are governed by different retention policies:

* User events

  User events include user creation or deletion, authentications, updates to the user record, and other transactions related to end-user activity. User events are retained for 90 days.

* PingOne configuration events

  Configuration events include configuration changes made to system settings, policies, applications, an integrations. Configuration events are retained for 2 years.

To retain PingOne data for longer than the standard retention periods, set up webhooks to stream the data to your own repository and configure your own retention policy. Learn more in [Webhooks](../integrations/p1_webhooks.html).

|   |                                                                                                                                                                                                                                       |
| - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | PingOne DaVinci data is retained for 30 days. Learn more in [Debugging and analytics](https://docs.pingidentity.com/davinci/davinci_best_practices/davinci_best_practices_debugging_and_analytics.html) in the DaVinci documentation. |

Learn more about auditing in PingOne in [Audit](../monitoring/p1_reporting.html).

## Webhooks

Use the **Webhooks** page in the PingOne admin console to set up subscriptions for auditing events.

When an event of interest occurs in PingOne, the event is pushed from PingOne to a third-party monitoring system. Webhooks are available in a Splunk-friendly format, a New-Relic-friendly format, and the Ping activity format, which is a versatile, generic JSON format also used by the PingOne API for accessing event data.

Learn more in [Webhooks](../integrations/p1_webhooks.html).

## PingOne API

Use the PingOne User Activities API to monitor user activities in PingOne. The service uses stream processors that listen to `users` and `login_attempts` events. These events are collected and presented by time period.

Learn more in [User activities](https://developer.pingidentity.com/pingone-api/platform/user-activities.html) in the PingOne API documentation.

## PingOne App for Splunk

Use the PingOne App for Splunk to correlate your PingOne webhook data into a meaningful dashboard. Create custom dashboards and reports, monitor activity data, and analyze event data over time.

Learn more in [Installing the PingOne app for Splunk](../developer_tools/p1_monitor_activity_splunk.html#p1-add-splunk-app).

## Dashboards

Use the **Dashboards** page in the PingOne console to view and monitor activities for a particular service. Each capability, such as Authentication, Authorization, Identity Verification, and so on, has its own dashboard.

Learn more in [Dashboards](../introduction_to_pingone/p1_introduction.html#p1-dashboards-intro).

## Alerts

Use the **Alerts** page in the PingOne console to set up alert messages based on the status of certain resources. For a complete list of available alerts, in the PingOne admin console, go to **Monitoring > Alerts**.

Learn more in [Alerts](../monitoring/p1_alerts.html).