---
title: Monitoring PingOne for Enterprise use
description: Use the reports and subscription tools to monitor PingOne for Enterprise user activity.
component: pingoneforenterprise
page_id: pingoneforenterprise:pingone_for_enterprise:p14e_monitoring_use
canonical_url: https://docs.pingidentity.com/pingoneforenterprise/pingone_for_enterprise/p14e_monitoring_use.html
revdate: December 28, 2023
---

# Monitoring PingOne for Enterprise use

Use the reports and subscription tools to monitor PingOne for Enterprise user activity.

Reports return a one-time report of data using either predefined or custom reports. PingOne for Enterprise logs events per report type and retains the logs for 1 year. For a list of the available event data, see [PingOne for Enterprise report types](p14e_report_types.html).

Subscriptions generate recurring reports of audit events for a report type. For example, you might create a subscription to the Administrator Login report type to receive the event data for each time a PingOne for Enterprise administrator signs on. A subscription can be either a Push or Poll type. See [Subscriptions](p14e_subscriptions.html) for more information.

You can view a list of users filtered by services such as single sign-on (SSO) *(tooltip: \<div class="paragraph">
\<p>The process of authenticating an identity (signing on) at one website (usually with a user ID and password) and then accessing resources secured by other domains without reauthenticating.\</p>
\</div>)* and multi-factor authentication (MFA) *(tooltip: \<div class="paragraph">
\<p>An electronic authentication method where a user is granted access only after presenting two or more verification factors for authentication.\</p>
\</div>)*. For more information, see [Monitoring service activity](p14e_monitor_service_activity.html).

Your PingOne for Enterprise billing is partially determined by the number of SSO transactions in your environments. For more information about monitoring SSO activity, see [PingOne for Enterprise usage monitoring](../p14e_monitoring_usage.html).
