{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":29797,"path":"it-operations-management/discovery/t_ConfigureDiscoveryEventFramework.md","title":"Configure Discovery to use Event Framework","bundle":null,"doc_type":null,"release":"australia","body":"\n# Configure Discovery to use Event Framework\n\nConfigure 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.\n\n## Before you begin\n\nConfirm the following:\n\n-   You're using Discovery Admin Workspace v1.9.0 or later.\n-   You're using the Xanadu Patch 9, Yokohama Patch 4, or later version of the ServiceNow AI Platform®.\n\nRole required: discovery\\_admin\n\n## About this task\n\nWhen 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. This approach introduces additional overhead and can lead to significant database churn, while offering limited control over how sensors are processed.\n\nThe Event Framework 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 is much more efficient and helps keep the system running smoothly.\n\n## Procedure\n\n1.  Navigate to **All** > **System Properties** > **All Properties**.\n\n2.  In the System Properties \\[sys\\_properties\\] table, select the **discovery.use.event.processing** property.\n\n3.  Set the **Value** field to **true**.\n\n4.  Select **Update**.\n\n\n## Result\n\nWhen 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.\n\n**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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/t_ConfigureBackgroundWorkerJobPriorityEF.md).\n\n-   **[Optimizing Discovery load for Event Framework](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/c_FineTuneDiscoLoadEF.md)**  \nYou can optimize Discovery properties to adjust throughput and enhance safety when pinning jobs.\n\n**Parent Topic:**[Advanced Discovery configuration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/c_DiscoveryExtendedCapabilities.md)\n\n"}}