Property reference

`glide.discovery.schedule_monitoring.dry_run`

Enables dry-run mode for Discovery schedule monitoring. When true, the job logs its decision in the Discovery Log without changing a status; the default false allows status changes when needed.

Default: false
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, Discovery schedule monitoring logs its decision in the Discovery Log but does not change the status state.
What area does it affect?	Discovery schedule monitoring
What does the default mean?	The default value is "false", which means this behavior is disabled by default.
When should you review it?	Review when testing monitoring decisions without changing Discovery status states.

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.schedule_monitoring.dry_run`
Type	boolean
Application	Not stated
Default value	`false`
Description	Not stated

Sources

Official references and nearby text excerpts where this property appears.

Brazil docs View supporting context

Context preview Snippet 1

... Note: On instances below ZP3 and YP9, the maximum number of IPv6 addresses per schedule must not exceed 5,000, which is also the default value in Yokohama and earlier releases. glide.discovery.schedule_monitoring.dry_run Determines whether the job will run in "dry run" mode. If set to true, the job will only log the decision in the Discovery Log but won't change the status's ...

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: DiscoveryStatusMonitor The monitor reads this setting and treats only the value “true” as enabled; otherwise it is disabled, with a default of false. The supplied code does not show what enabling it changes for users or administrators. /sys_script_include.do?sys_id=64949c364370311062f7f57c0ab8f26a

Script include: DiscoverySysTriggerInsertFailureMonitor The setting is read when this monitor is initialized and is true only when its value is “true”; otherwise it is false. If the setting is absent, it defaults to false, and the shown code does not reveal what this changes for users or admins. /sys_script_include.do?sys_id=ea47ee1e7fd0261084afda37bc866558

More in `glide.discovery`

Other properties in the same namespace.

glide.discovery.schedule.autogenerate.subnet_batch_size Sets the number of subnets handled in each batch during automatic discovery schedule generation. glide.discovery.schedule.autogenerate.use_location_grouping Determines whether automatically generated discovery schedule groups include each subnet’s location. glide.discovery.schedule_ipv4_limit Sets the address-count limit used to split IPv4 ranges across auto-generated IPAM Discovery schedules; the… glide.discovery.schedule_ipv6_limit This property defines the upper limit for IPv6 addresses in auto-generated discovery schedules, facilitating… glide.discovery.schedule_monitoring.schedule_types_to_monitor Provides a comma-separated list of discovery schedule types for status monitoring, matched against the… glide.discovery.schedule_monitoring.should_force_ecc_validation When set to true, enables forced ECC validation in Discovery schedule monitoring; the default false setting… glide.discovery.schedule_monitoring.stale_check_seconds Sets the inactivity period, in seconds, after which a Discovery schedule status is considered stale. glide.discovery.sensor.ci_lock When enabled, this property allows Discovery sensors to secure a lock on the CI prior to processing…

All 168 properties in glide.discovery →