---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# View event processing statistics

# View event processing statistics {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Extract statistics from your instance to ensure that performance is not affected and extract metrics related to event processes to monitor event processing status.{#monitor-event-processing-metrics__xmlstats4em}

## Before you begin

Ensure that the Event Management - Collect xmlstats job is active. Configure this scheduled job by navigating to System DefinitionScheduled 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://servicenow-prod.fluidtopics.net/CJjX_bg6N5kwzOWu_301xg "Set the time period, in seconds, for collecting event processing statistics. For example, you can set a time period twice as long as the default 60 seconds to collect more statistics.").

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 self-health monitoring statistics for Metric Intelligence](https://servicenow-prod.fluidtopics.net/V9pydSXI88YJCqpSAHw1~A "Monitor the status of components and processes of Metric Intelligence. Use the XMLStats page to view statistics and diagnostic details that can help with troubleshooting issues with Metric Intelligence.").

## 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.
{#monitor-event-processing-metrics__steps_hpp_h22_fhc}

## Result

## Sample output after running the XML Stats script {#monitor-event-processing-metrics__example_ipp_h22_fhc}

    <xmlstats created="Tue Oct 23 04:01:25 PDT 2018" includes="XMLStatsEm" version="2">
    <itom_event_management>
    <event_processing>
    <processed count="47" max_process_time="10" mean_process_time="5" record_time="2018-10-23 11:00:41"/>
    <ready count="7" oldest_ready_event="37" record_time="2018-10-23 11:00:41"/>
    <error count="5" record_time="2018-10-23 11:00:41"/>
    <total_created count="5" record_time="2018-10-23 11:00:41"/>
    </event_processing>
    </itom_event_management>
    </xmlstats>

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.
{#monitor-event-processing-metrics__table_vtl_5kd_wfb__entry__2}

| 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. |
[Table 1. Event processing statistics]

{#monitor-event-processing-metrics__table_vtl_5kd_wfb}
* **[Enable processing of event process statistics](https://servicenow-prod.fluidtopics.net/z3I9W63y75nVGR4FuzUHHw)**   
  Enable the system property that switches on statistics processing for events to let the platform collect and analyze metrics such as event volume, processing flow, and handling time. This helps you monitor system performance, identify bottlenecks, and optimize event handling for faster and more efficient operations.
* **[Configure statistics processing period](https://servicenow-prod.fluidtopics.net/CJjX_bg6N5kwzOWu_301xg)**   
  Set the time period, in seconds, for collecting event processing statistics. For example, you can set a time period twice as long as the default 60 seconds to collect more statistics.

*[\>]: and then