discovery.use.event.processing The discovery.use.event.processing property enables the use of the Event Framework for processing Discovery jobs. When set to true, it improves efficiency by reducing database churn and managing job processing more effectively.
falseThe answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? | This property determines whether Discovery utilizes the Event Framework for processing jobs, which enhances performance and resource management. |
|---|---|
| What area does it affect? | Discovery job processing |
| What does the default mean? | The default value is "false", which means this behavior is disabled by default. |
| When should you review it? | Review this property when optimizing Discovery performance or troubleshooting processing issues. |
Raw metadata from the property record.
| Property name | discovery.use.event.processing |
|---|---|
| Sys ID | 9eeffa0687079a101b5987bd0ebb35d9 |
| Type | boolean |
| Application | Global |
| Default value | false |
| Description | When false Discovery will create 'run once' sys_trigger jobs to process ecc_queue inputs. When true Discovery will use event processing. |
| Updated | 2025-04-08 11:02:46 |
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.event.separate.cloud.events
When enabled, this property allows Discovery to utilize separate event queues for IP and cloud discoveries, im
discovery.mssql.cluster.instance.postsensor.delete
It allows the system to delete MSSQL instances and related databases from passive cluster nodes after failover