Property reference

`glide.discovery.count.use_optimized_counter`

Enables optimized updates to Discovery's started and completed status counts. When enabled by default, these updates bypass most business rules on discovery_status, with exceptions for specific starting and completed count changes.

Default: true
Type: boolean
Application: Not stated
Category: CMDB & Discovery

Key questions about this property

The answers below summarize the purpose, scope, default effect, and review scenarios for this property.

What does it do?	When enabled, uses optimized updates for Discovery's started and completed counts, bypassing business rules on discovery_status except for specific count-change conditions.
What area does it affect?	Discovery status tracking
What does the default mean?	The default value is "true", which means this behavior is enabled by default.
When should you review it?	Review when changing Discovery status-count update behavior or troubleshooting business rules tied to discovery_status.

Property record

No out of the box record exists. ServiceNow scripts read this property and use the default value shown until you create it.

Property name	`glide.discovery.count.use_optimized_counter`
Type	boolean
Application	Not stated
Default value	`true`
Description	Not stated

Sources

Official references and nearby text excerpts where this property appears.

Brazil docs View supporting context

Context preview Snippet 1

... Type: true | false • Default value: true glide.discovery.certs.slack_channel_id Certificate Inventory and Management: Indicates the Slack channel ID where certificate notifications are sent. • Type: string • Default value: empty glide.discovery.count.use_optimized_counter Executes optimized code for updating discovery_status.started and discovery_status.completed counts. If set to true, business rules on discovery_status won't execute when "started" or "completed" is changed. There are two exceptions: 1. ...

Used in

Out of the box artefacts that read this property. Append the path to your instance URL to open the record and see how the value is used.

Script include: DiscoveryStatus The setting controls whether starting a discovery triggers the status update that changes its state from Starting to Active; false skips that update. If no value is set, it defaults to true. /sys_script_include.do?sys_id=0923b5ee0ab30150007c408f74342949

More in `glide.discovery`

Other properties in the same namespace.

glide.discovery.cloud.filterout_databrick_vms This property determines whether temporary Azure Databricks VMs are excluded from discovery results, helping… glide.discovery.cloud.service_account_batch Sets the batch size for processing cloud discovery service-account configurations, defaulting to 20 when the… glide.discovery.cloud_discovery_result.tables_to_exclude This property configures the exclusion of specified tables from resource counts in Cloud Discovery results… glide.discovery.collector.vcenter.event_window Sets the window for comparing vCenter events when deciding whether an event should trigger discovery; a… glide.discovery.debug.ci_identification This property activates debug logging specifically for CI Identification, allowing for more detailed… glide.discovery.debug.classification When set to true, glide.discovery.debug.classification writes Discovery classification details to the system… glide.discovery.debug.network_discovery This property activates extensive logging for network discovery processes, aiding in troubleshooting and… glide.discovery.delete_strategy.ci_batch_size_for_deletion Sets the number of configuration items grouped into each deletion batch, defaulting to 500 when no value is…

All 168 properties in glide.discovery →