---
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 a single queue for Cloud-based and IP-based events

# Configure a single queue for Cloud-based and IP-based events {#ariaid-title1}

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

Configure Cloud-based and IP-based events to share a single queue, which helps reduce the impact of Discovery on app nodes.

## Before you begin

Confirm the following:

* Discovery Admin Workspace is using version 1.9.0 or later.
* ServiceNow AI Platform® is using XP9, YP4, or later than YP4.
* The discovery.use.event.processing system property is turned on. For more information, see [Configure Discovery to use Event Framework](https://servicenow-prod.fluidtopics.net/35XxjR9b1xrfGrR4uQRZrw "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.").
{#t_CombineCloudIPJobQueueEF__ul_m31_scl_b1c}

Role required: discovery_admin

## About this task

When using a single queue, Cloud Discovery jobs frequently have higher priority than IP-based Discovery jobs. Separating Cloud-based and IP-based job queues helps avoid interference between Discovery types. However, balancing Discovery throughput and instance impact involves trade-offs.  
{#t_CombineCloudIPJobQueueEF__table_qfm_kwn_gfc__entry__2}

| Separate queues | Single queue |
|-|-|
| More worker threads, which means more database activity | Fewer worker threads, which means less database activity |
| More impact on jobs unrelated to Discovery | Less impact on jobs unrelated to Discovery |
| Cloud Discovery doesn't impact IP Discovery | Cloud Discovery can preempt IP Discovery |
[Table 1. Instance impact based on queue configuration]

{#t_CombineCloudIPJobQueueEF__table_qfm_kwn_gfc}

## Procedure

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

*[\>]: and then