--- title: View event processing statistics description: Extract statistics from your instance to ensure that performance is not affected and extract metrics related to event processes to monitor event processing status. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/it-operations-management/event-management/monitor-event-processing-metrics.html release: australia product: Event Management classification: event-management topic_type: task last_updated: "2026-03-12" reading_time_minutes: 2 breadcrumb: [Processing Events, Configure, Event Management, ITOM AIOps, IT Operations Management] --- # View event processing statistics Extract statistics from your instance to ensure that performance is not affected and extract metrics related to event processes to monitor event processing status. ## Before you begin Ensure that the **Event Management - Collect xmlstats** job is active. Configure this scheduled job by navigating to **System Definition** > **Scheduled Jobs**. You can control the processing of event statistics using the **evt\_mgmt.event\_processing\_stats\_period** property. For information about configuring this property, see [Configure statistics processing period](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/event-management/add-property-statistics-processing-period.md). Role required: evt\_mgmt\_operator ## About this task You can view key metrics from the instance to ensure that performance is not affected and monitor the status of the processing of events. For more information about viewing self-health monitoring statistics, see [View Metric Intelligence self-health statistics](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/metric-intelligence/xmlstats-oi-self-health.md). ## Procedure 1. In a browser where the instance is running, run the XML Stats script by appending the following text to the instance URL: `xmlstats.do?include=XMLStatsEm` 2. Press **Enter**. 3. Monitor the event processing metrics that are reported to ensure that events are processed according to accepted benchmark values. ## Result ## Sample output after running the XML Stats script ``` ``` The event processing metrics in the report are described in the following table. **Note:** The default processing cycle is events created in the last hour and updated in the last minute.
Metric Description
Event processing statistics
processed count=n Number of events processed by the instance.
max\_process\_time=n Longest time taken by the instance to process an event.
mean\_process\_time=n Average time taken by the instance to process the events in this cycle.
Event ready statistics
ready count=n Number of events that are in Ready state and are available to be processed.Default processing cycle: events created in the last hour and updated in the last minute.
oldest\_ready\_event=n Longest time taken by an event to remain in Ready state. If this metric has a value that is bigger than your benchmark figure, investigate the event further to determine what is impeding the processing.Default processing cycle: events created in the last hour.
Other processing statistics
error count=n Number of events for which errors were reported.Default processing cycle: events created in the last hour and updated in the last minute.
total\_created count=n Overall number of events that were processed during this event processing cycle.Default processing cycle: events created in the last hour.