---
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


---

# Configure Discovery to use Event Framework

# Configure Discovery to use Event Framework {#ariaid-title1}

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

Configure Discovery to process jobs using the Event Framework method, which enables you to manage discovery throttling effectively and prioritize tasks based on their importance in the queue.

## Before you begin

Confirm the following:

* Discovery Admin Workspace is using version 1.9.0 or later.
* ServiceNow AI Platform is using version XP9, YP4, or later than YP4.

{#t_ConfigureDiscoveryEventFramework__ul_m31_scl_b1c}

Role required: discovery_admin

## About this task

When not using the Event Framework method, Discovery creates a one-time Schedule Item \[sys_trigger\] record for each External Communication Channel (ECC) queue sensor or pattern input record. After the task is processed, the system scheduler deletes
the sys_trigger record. This approach introduces additional overhead and can lead to significant database churn, while offering limited control over how sensors are processed.

The Event Framework method reduces database churn by cycling through multiple event tables over time. Instead of deleting old records one by one, it clears out entire tables when they're no longer needed and reuses them. This
approach helps keep the system running smoothly and efficiently.

## Procedure

1. Navigate to AllSystem PropertiesAll Properties.
2. In the System Properties \[sys_properties\] table, select the discovery.use.event.processing property.
3. Set the Value field to true.
4. Select Update.

## Result

When an input record is added to the ECC Queue, a business rule is triggered, which fires an event. The system processes these events at regular intervals with a default priority of 100.  
Note:  
To update a job priority, configure the com.glide.queue.discovery.sensors.processing_jobs.priority and com.glide.queue.discovery.cloud.sensors.processing_jobs.priority system properties. For more information, see [Configure background worker job priority for Event Framework](https://servicenow-prod.fluidtopics.net/_RUni84J~Qt91EcLdGh55Q "Configure the job priority of background workers to help prevent noncritical tasks from preempting important work, which promotes system efficiency and stability.").
* **[Optimizing Discovery load for Event Framework](https://servicenow-prod.fluidtopics.net/3lUFGuQ~XmMHWG42vO8y1w)**   
  You can optimize Discovery properties to adjust throughput and enhance safety when pinning jobs.

*[\>]: and then