discovery.event.separate.cloud.events The discovery.event.separate.cloud.events property enables the use of distinct event queues for IP and cloud discovery. This separation enhances resource allocation and processing efficiency, allowing both types of discovery to operate without interference.
trueThe answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? | When enabled, this property allows Discovery to utilize separate event queues for IP and cloud discoveries, improving processing times and resource management. |
|---|---|
| What area does it affect? | Discovery event processing |
| What does the default mean? | The default value is "true", which is the baseline setting used unless it is changed. |
| When should you review it? | Review this property when configuring Discovery settings or optimizing resource allocation. |
Raw metadata from the property record.
| Property name | discovery.event.separate.cloud.events |
|---|---|
| Sys ID | 820a5bf993402e586da9bc447aba101a |
| Type | string |
| Application | Global |
| Default value | true |
| Description | When true Discovery will use separate event queues for IP vs. cloud discovery. This allows IP and cloud discovery to run without interfereing with each other but also allows Discovery to use more instance resources. When false all processing will use the discovery.sensor queue. |
| Updated | 2025-03-03 15:15:37 |
Official references and nearby text excerpts where this property appears.
discoveryOther properties in the same namespace.
discovery.event.pin.jobs
When enabled, this property assigns Discovery jobs to specific nodes, limiting job assignment flexibility but
discovery.mssql.cluster.instance.postsensor.delete
It allows the system to delete MSSQL instances and related databases from passive cluster nodes after failover
discovery.use.event.processing
This property determines whether Discovery utilizes the Event Framework for processing jobs, which enhances pe