Discovery properties
Discovery properties allow you to control several aspects of the horizontal discovery process.
For information about the Discovery properties that Agent Client Collector uses, see Using push-based Discovery and horizontal IP-based Discovery together.
Edit the following Discovery properties by navigating to .
IP properties
| Field | Description |
|---|---|
| glide.discovery.exclude_ip_sync_classes | Defines CI classes whose IP addresses shouldn’t be substituted if the address returned by Discovery doesn’t match one of the devices' NICs. Use a comma-separated list to define multiple classes. By default, the
system uses the management IP of a load balancer returned by Discovery in the CI record, rather than substituting it for the IP address of one of the load balancer's NICs.
|
| glide.discovery.enforce_unique_ips | Enforce unique IP addresses: Ignores the IP address after Discovery encounters subsequent devices that use the same IP address. Each time a computer, printer, or network gear with a valid IP address is discovered, any other devices with the same IP address have their IP address field cleared. If inactive, stores the IP address for each device.
|
Network properties
| Field | Description |
|---|---|
| glide.discovery.bgp_router_disable | BGP router exploration disable: Disables running the SNMP – Routing probe or pattern when discovering a router running the BGP protocol. Normally such exploration IS inactive because of the huge size of BGP routing tables, and because generally such routers are only operating at the edge of large networks where further network discovery would be irrelevant. This value could be set to false if your organization only uses BGP routers as edge routers between relatively small networks (such as between buildings on a single campus). If you must populate the [discovery_device_neighbors] table during horizontal layer 2 discovery of the bgp-enabled devices, set the BGP router exploration disable property to No. Notice that enabling this property can cause performance issues including out-of-memory issues on the MID Server.
|
| glide.discovery.debug.network_discovery | Network discovery debugging: Enables extensive logging of all Network Discovery activities on the instance.
|
| glide.discovery.discoverable.network.max.netmask.bits | Maximum netmask size for discoverable networks (bits): The maximum number of bits in a regular netmask for networks that are discovered by Network Discovery. A regular netmask is a netmask that can be expressed in binary as a string of ones followed by a string of zeroes. For example, 255.255.255.0 is regular and 255.255.255.64 is irregular. Regular networks are commonly expressed like: 10.0.0.0/24, which means a network address of 10.0.0.0 with a netmask of 255.255.255.0. Larger bit numbers mean networks with smaller numbers of addresses in them. For example, the network 10.128.0.128/30 has four addresses in it: one network address (10.128.0.128), one broadcast address (10.128.0.131), and two usable addresses (10.128.0.129 and 10.128.0.130). Small networks are commonly configured in network gear to provide loopback addresses or networks used strictly by point-to-point connections. Since these sorts of networks generally don't need to be discovered by Network Discovery, it would be useful to filter them out. By setting this property to a value of 1 through 32, you can limit the sizes of regular networks that are discovered. Setting it to any other value causes all networks to be discovered. Irregular networks are always discovered. The default value is 28, which means that regular networks with 8 or fewer addresses cannot be discovered.
|
| glide.discovery.network_owner_method | Network router selection method: This property controls the method used to decide (during Network Discovery) which router should be selected as the router to be associated with a given IP Network. The possible values are:
|
| glide.discovery.physical_interface_types | Physical interface types: A comma-separated list of interface types that are considered physical for the purposes of network discovery. If a router (or device capable of routing) has an interface of
this type, the networks connected to that interface are considered locally connected to that device. The default interface types include Ethernet, 802.11, and Token Ring types. Interface type numbers are defined in
the SNMP MIB-2, specifically in OID 1.3.6.1.2.1.2.2.1.3.
|
| glide.discovery.switch_interface_types | Switch interface types: A comma-separated list of interface types that are considered. Interface type numbers are defined in the SNMP MIB-2, specifically in OID 1.3.6.1.2.1.2.2.1.3. Devices with any interface
types that do NOT appear in this list are classified as routers, when they have routing. A complete list of the interface type numbers may be found on the IANA web site, in the section "ifType definitions".
|
Other Discovery properties
| Field | Description |
|---|---|
| com.snc.use_external_credentials | Allows the use of external storage of credentials.
|
| com.glide.processing.framework.max_thread_utilization_percentage | Enables you to modify the scale factor for the discovery.sensor and discovery.cloud.sensor queues. Increasing the value allows you to increases the scale factor, which
subsequently increases the number of worker threads per app node.
Note: This behavior only applies when discovery.use.event.processing is set to true. |
| com.glide.queue.discovery.cloud.sensors.processing_jobs.priority | Manages the background job's worker priority for Cloud-based Discovery jobs when using Event Framework. Increasing the value decreases the priority.
Note: This behavior only applies when discovery.use.event.processing is set to true. |
| com.glide.queue.discovery.sensors.processing_jobs.priority | Manages the background job's worker priority for IP-based Discovery jobs when using Event Framework. Increasing the value decreases the priority.
Note: This behavior only applies when discovery.use.event.processing is set to true. |
| discovery.event.pin.jobs | Enables event processors to execute on specific nodes. When set to true, jobs are assigned to nodes to distribute the work evenly. If set to false, jobs are
randomly assigned, which may increase discovery throughput.
Note:
This behavior only applies when discovery.use.event.processing is set to true. |
| discovery.event.separate.cloud.events | Reduces processing time by separating the discovery.sensor and discovery.cloud.sensor event queues for cloud and IP-based discoveries. When this property is set to
false, event processing will only use the discovery.sensor queue.
Note:
This behavior only applies when discovery.use.event.processing is set to true. |
| discovery.use.event.processing | Enables Discovery to use the Event Framework when processing jobs.
|
| glide.discovery.active_processes_filter |
Active Processes Filter: Optimization for application dependency mapping. Filters the active processes returned by Discovery to only those that have a match in the Process Classification table.
|
| glide.discovery.adme.aggregation_interval | ADME - Aggregation interval (sec): How often to aggregate instantaneous data into chunks in seconds. It must be a minimum of 60 seconds and it must be a multiple of ADME Sampling interval.
|
| glide.discovery.adme.base_dir_unix | ADME - Unix Base Dir: An existing directory on the target UNIX machines to be used as a workspace. Must be an absolute path to the directory.
|
| mid.powershell.target_base_dir | Powershell - Target Base Dir: A network share on the target Windows machines to be used as a workspace.
|
| glide.discovery.adme.max_total_samples | ADME - Max total samples: The limit of samples being taken by the script. The script will stop running after this number of samples are taken.
|
| glide.discovery.adme.rolling_window_size | ADME - Rolling window size: How many recently aggregated chunks to keep. An aggregated chunk consists of ADME Aggregation interval divided by ADME Sampling interval samples. Only the newest chunks are kept.
|
| glide.discovery.adme.sampling_interval | ADME - Sampling interval (sec): How often to sample process and connection data in seconds. Must be a minimum of 5 seconds.
|
| glide.discovery.adm.update.applications |
Controls if application CIs should be updated based on running process status. When Discovery rediscovers the server and notices that a previously running process is no longer active on cmdb_running_process record, Absent is set to true. In addition, on
related application CI, install_status is updated from installed to absent. On subsequent scans, if the running process is back online on the related application CI, install_status is reverted to installed.
Note: This behavior will only work for application CIs that are discovered using patterns.
|
| glide.discovery.allow_loopback_adapters | Loopback adapter filter: Allows network loopback adapters on SNMP devices to be discovered instead of being filtered out during Discovery. When this property is set to true, network
loopback addresses are discovered and added to the CMDB.
|
| glide.discovery.application_mapping |
Application mapping: Enables the application mapping portion of Discovery Important:
Disabling this property disables the creation of relationships between applications but doesn’t disable the ADM probes and sensors, nor does it prevent process
classification.
|
| glide.discovery.certs.cert_admin_user_id |
Certificate Inventory and Management: Holds the user ID of the user who will be referenced in the certificate task and incident, created via Scheduled Job.
|
| glide.discovery.certs.days_before_expiration_to_create_renewal_task |
Certificate Inventory and Management: Number of days before certificate expiration that a renewal task should be created.
|
| glide.discovery.certs.enable_incident_creation_for_expired_certificates |
Certificate Inventory and Management: Enables the Scheduled Job to create the incidents for expired certificates, for example, certificates whose validity is past current system date or time. By default, this property is enabled.
|
| glide.discovery.certs.enable_renewal_task_creation_for_discovered_certificates |
Certificate Inventory and Management: Enables renewal task creation for all discovered certificates. By default, this property is enabled.
|
| glide.discovery.certs.slack_channel_id |
Certificate Inventory and Management: Indicates the Slack channel ID where certificate notifications are sent.
|
| 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:
|
| glide.discovery.debug.ci_identification | CI identification debugging: If set to true, enables debug logging (into the CI Identification Log) for CI Identification.
|
| glide.discovery.discover_aws_ec2_host_metadata | When doing IP-based discovery against a given host, also run probes that retrieve AWS EC2 metadata.
|
| glide.discovery.discover_azure_host_metadata | When doing IP-based discovery against a given host, also run probes that retrieve Azure metadata.
|
| glide.discovery.discover_software | Discover software packages: Enable the discovery of software packages.
|
| glide.discovery.domain.name.nbt | Set OS domain name by NBT or WMI. If set to true, Windows domain name is set by NBT. Otherwise it’s set by WMI.
|
| glide.discovery.enable_adme | ADME: Enable enhanced ADM probe. If set to true, the ADM Enhanced probe is triggered and only fall back to the ADM probe as needed.
|
| glide.discovery.enable_file_tracking |
Enable configuration file tracking as part of the Pattern based Horizontal Discovery. If set to true, the system enables you to specify paths of configuration files for applications that are discovered by patterns. You can track and compare tracked configuration files.
|
| glide.discovery.enable_mac_address_verification |
Enables MAC address verification to determine if a device has changed its IP address during a discovery. If set to true, Discovery passes the MAC address of a device being discovered to the MID Server so that probes can determine if the IP address has changed while Discovery is running. If the device has changed IP addresses, then Discovery stops processing that IP address and updates the Discovery log with a warning message. Discovery doesn’t stop processing other IP addresses.
Open the System Properties [sys_properties] table to find this property. |
| glide.discovery.enable.software_filter |
Windows software filter: Enable Windows software filtering for Discovery.
|
| glide.discovery.enable.software_simplify | Enables cleanup for software’s name and version. If set to true, it removes any appended version or commonly found phrases from the name and removes leading 0s in the version. If set to
false, raw data is persisted in the table. Use with the glide.discovery.enable.software_simplify_sccm property to avoid software data discrepancy between Discovery
and SCCM.
Note: Once the property is set to false, to disable the cleanup, duplicate records are generated for a given software. Name and Version are the primary identifiers. |
| glide.discovery.enable.software_simplify_sccm | Enables cleanup for SCCM software. If set to true, Discovery changes the Name of the software to be the same as SCCM. If set to false, Discovery doesn’t clean up
the Name. Use with the glide.discovery.enable.software_simplify property to avoid software data discrepancy between Discovery and SCCM.
|
| glide.discovery.enable_ssm | Enables AWS SSM-based discovery.
|
| glide.discovery.ssm.enable_windows | Enables AWS SSM-based discovery on Windows machines as a high-level system user that can run any command.
|
| glide.discovery.file_tracking.max_file_size | File Tracking: The maximum file size for tracked configuration file content.
|
| glide.discovery.file_tracking.max_files_per_ci | File Tracking: The maximum number of tracked configuration files per CI.
|
| glide.discovery.file_tracking.change_limit_count | File Tracking: Number of changes allowed on a tracked configuration file in the defined time window.
|
| glide.discovery.file_tracking.change_limit_days | File Tracking: Time window (in days) that limits the number of changes on a tracked configuration file.
|
| glide.discovery.fqdn.regex | DNS Host Name And Domain Name Regex: The default parsing of FQDN (Fully Qualified Domain Name) is to pick the first name separated by dots as the host name and the rest of the names as the domain name. For
example, "machine1.testlab.service-now.com" has host name of "machine1" and domain name of "testlab.service-now.com". The property allows regex with two capturing groups with the first group representing the host
name and the second group the domain name.
|
| glide.discovery.hostname.always_update | Always update host name. If set to true, discovery always updates the host name with the most recently discovered value contingent upon the source being trusted. Note that this may
result in hand-entered values being overwritten. This property is only applicable for Probe-based Discovery.
|
| glide.discovery.hostname.case | Host name case. If Lower case is selected, always translate the host name into lower case. If Upper case is selected, always translate the host name to upper case.
If No change is selected, leave the host name intact. This primarily affects host names discovered with NETBIOS, though some non-standard DNS systems may also return some or all of the name
in upper case.
|
| glide.discovery.hostname.dns_nbt_trusted | DNS or NetBIOS is trusted host name source: If set to true, trust the device name discovered via DNS or NetBIOS. If checked, CI's host name found via DNS or NBT is used. Note: For Linux, AIX, and Solaris patterns, do not use the DNS name as the host name.
|
| glide.discovery.hostname.include_domain | Includes domain name in host name: If set to true, include the domain name as part of the host name. For example, "bosco.service-now.com" instead of "bosco". Note: For AIX and Solaris patterns, do not use the DNS name as the host name.
|
| glide.discovery.hostname.snmp_trusted | SNMP is trusted host name source: If set to true, trust the device name discovered via SNMP. If checked, any device name found via SNMP is used instead of the name found by a reverse DNS
lookup.
|
| glide.discovery.hostname.ssh_trusted | SSH is trusted host name source: If set to true, trust the device name discovered via SSH. If checked, any device name found via SSH is used instead of the name found by a reverse DNS
lookup. Note: For Linux, AIX, and Solaris patterns, do not use the DNS name as the host name.
|
| glide.discovery.hostname.wmi_trusted | WMI is trusted host name source: If set to true, trust the device name discovered via WMI. If checked, any device name found via WMI is used instead of the name found by a reverse DNS lookup.
|
| glide.discovery.ip_based.active | This allows scans on all IP Address of the same device in the same Discovery schedule to go through full cycle. This is set to true for probe-to-pattern migrated instances, Discovery doesn’t attempt extra IP Address detection.
|
| glide.discovery.ip_service_affinity |
IP service affinity: If set to true, IP service affinity is enabled. IP service affinity allows Discovery to remember the last port of the IP address that was discovered. Note:
You must enable ip_service_affinity records if you’re using multiple SSH ports.
|
| glide.discovery.L3_mapping | Map servers and network devices to routers and layer-3 switches If the "L3 mapping" property is enabled, it maps servers and network gears to its associated routers and layer-3 switches.
|
| glide.discovery.log_message_length |
Limits the maximum message length that is displayed in Discovery Log table. A value of 0 or any negative number disables this limit.
|
| glide.discovery.mark_esx_servers_as_absent | If this property is set to true, the ESX Servers are marked as absent instead of retired if the ESX server isn’t found in the payload.
|
| glide.discovery.max_concurrent_invocations_per_schedule | Maximum concurrent invocations per schedule: Prevents an unbounded number of invocations from inundating the system when a schedule takes longer than the time between invocations. The value is an integer
defining the maximum number of automated invocations of the same schedule that may proceed at one time. If the limit has been reached subsequent scheduled invocations are canceled. The default value is 3. A value
of 0 or any negative number disables this restriction.
Note: This property does not apply to schedules that have a 'Run after' configuration set to 'Even if canceled'. |
| glide.discovery.network_discovery.functionality | Networks discovery functionality: The Functionality used to discover networks. Usually this should be SNMP only.
|
| glide.discovery.perf.metrics.enable_collection | Whether to collect Discovery performance metrics.
|
| glide.discovery.perf.metrics.rollup_by_build | Whether to aggregate individual Discovery performance metrics into a roll-up table that groups by discovery build.
|
| glide.discovery.perf.metrics.rollup_by_status | Whether to aggregate individual Discovery performance metrics into a roll-up table that groups by discovery status.
|
| glide.discovery.perf.metrics.rollup_by_target | Whether to aggregate individual Discovery performance metrics into a roll-up table that groups by target IP address.
|
| glide.discovery.populate_software_instance_table |
If set to true, Discovery populates these tables for software discovery:
cmdb_software_instance and cmdb_sam_sw_install
Use this property only if you were using Software Asset Management with Discovery in pre-Jakarta releases and want to keep populating the Open the System Properties [sys_properties] table to find this property. |
| glide.discovery.roundingInterval.cpu | CPU speed rounding: Enter the number to round the CPU speed to. The units are in MHz.
|
| glide.discovery.roundingInterval.ram | Memory rounding: Enter the number to round the computer RAM to. The units are in MB.
|
| glide.discovery.save_pattern_log | Controls whether pattern logs are saved during discovery execution. This property helps enhance performance by reducing database interactions.
If set to false, the system saves the pattern log only when it is important to display information (for example, when a failure occurs). This further improves performance by minimizing unnecessary saves. Note: Regardless of the property value, pattern logs are always saved if the pattern status is failure. |
| glide.discovery.schedule.autogenerate.debug | Enables detailed logging for troubleshooting. If set to true, the job’s detailed logging output will appear in the System Log [sys_log] table with the source DiscoveryIPAMIntegration.
|
| glide.discovery.schedule.autogenerate.group | Groups auto-generated IPAM Discovery schedules by a specific tag or attribute. For example, entering "location" as the value would group the schedules by their associated locations.
|
| glide.discovery.schedule_ipv4_limit | Defines the maximum number of IPv4 addresses that can be included in a single auto-generated IPv4 Discovery schedule.
|
| glide.discovery.schedule_ipv6_limit | Defines the maximum number of IP6 addresses that can be included in a single auto-generated IPv6 Discovery schedule.
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 state, otherwise the job will change the state of the status if needed.
|
| glide.discovery.schedule_monitoring.schedule_types_to_monitor | Determines the type of statuses to track. The value can be found on the "Discover" attribute on the schedule.
|
| glide.discovery.schedule_monitoring.stale_check_seconds | Determines the number in seconds in which a status is considered stale. A stale status is a status that was not updated for the last X seconds.
|
| glide.discovery.sensors.fire_ssh_probe | In case the VIPs (Load Balancer Virtual Services) didn’t return as part of the SNMP Probe payload, fire the SSH Probe. Select this option to use the SSH port on the load balancer, rather than just using SNMP.
|
| glide.discovery.sensors.netapp_native_7mode | For 7-Mode NetApp storage servers, use native discovery instead of SMI-S. |
| glide.discovery.sensors.netapp_native_cluster_mode | For Cluster Mode NetApp storage servers, use native discovery instead of SMI-S. |
| glide.discovery.sensors.save_attachments | Save ECC queue attachments: The normal behavior for discovery sensors is to delete attachments to ECC queue entries upon successful sensor processing. Setting this property to true overrides this behavior, and
forces attachments to be preserved. This would normally only be useful for debugging purposes.
|
| glide.discovery.shazzam_ranges_json | Use JSON for IP ranges in Shazzam: If set to true, discovery encodes Shazzam's IP ranges as JSON, dramatically reducing the payload size.
|
| glide.discovery.shazzam_simplify_ranges |
If set to true, Shazzam detects if an IP is included in multiple ranges of the same Discovery schedule and removes the duplicate IP from all but one range. Deduplication is limited to schedules with a single behavior. Schedules with multiple behaviors work, but duplicate IPs aren’t removed.
|
| glide.discovery.software_filter_keys | Windows software filters: If Windows software filtering is enabled, when the name of a discovered software contains any of the comma-separated values, it’s filtered out.
|
| glide.discovery.software_sccm_managed |
Windows software is SCCM managed: If set to true, Discovery won’t populate software for computer CIs also managed by SCCM.
|
| glide.discovery.use_cmdb_identifiers |
CMDB Identifiers: If set to true, identification and reconciliation will be handled by the CMDB API instead of through the old Discovery implementation.
|
| glide.discovery.use_probe_results_cache | Use probe results cache: If set to true, the cache is checked to see if the results of the probe must be processed by a sensor. It only needs to be processed if the results have changed
from the last discovery run.
Note:
In previous releases, this property was true by default. The value in this property isn’t changed during an upgrade to Kingston. |
| glide.discovery.virtual_interface_types | Virtual interface types: List of interface types (comma-separated) that can be considered "virtual" for the purposes of network discovery. In other words, if a router (or device capable of routing) has an
interface of this type, the networks connected to that interface are considered virtually connected to that device. The default interface types include the propVirtual type. Interface type numbers are defined in
the SNMP MIB-2, specifically in OID 1.3.6.1.2.1.2.2.1.3.
|
| glide.discovery.warn_minor_version |
Warn on Minor Version Mismatch: If set to true, warnings are logged when minor_version mismatches are detected during Discovery sensor processing.
|
| glide.ecc_agent.validated.override | An override for the ecc_agent validated field: If set to true, ecc_agent records will always be treated as valid.
Navigate to to find this property. |
| glide.eccprobe.awsrestprobe.max_retries | Set the maximum number of times the AWS request will be retried if a rate limit exceeded error occurs. Maximum value is 10. Note that retries use exponential backoff (2^x). Setting negative values is
equivalent to setting the maximum value.
|
| glide.eccprobe.awsrestprobe.max_wait | Set the maximum total amount of time (seconds) the AWS request attempts to retry. Maximum value: 2046 seconds. Setting negative values is equivalent to setting the maximum value.
|
| glide.eccprobe.max_queued_probes_per_run | Set the maximum number of probes a node can pick up during a run.
|
| glide.eccprobe.node_agent_id | ECC queue entries with "mid.server.${VALUE}" will be picked up and processed by the nodes. This must be unique and not the same as any MID server name.
|
| sn_disco_firewall.default.rule.task.policy.owner.group |
Firewall Audits and Reporting: Indicates the name of the assignment group that owns or is assigned to firewall rule tasks
|
| sn_disco_firewall.default.rule.task.approval.group |
Firewall Audits and Reporting: Indicates the name of the approval group that is used to approve the firewall rule tasks.
|
| sn_disco_certmgmt.enable_csr_generation | Enables automatic CSR generation on the Certificate Inventory and Management Request New Certificate and Request New Ceriticate (Automated) forms. This feature is
disabled by default for security.
|
| sn_disco_certmgmt.private_key_size | Changes the private key size when using automatic CSR generation on the Certificate Inventory and Management Request New Certificate and Request New Ceriticate
(Automated) forms. This property accepts values: 512 | 1024 | 2048 | 4096.
|
| sn_disco_workspace.discovery_schedule_anomaly_detection_disabled | Discovery Admin Workspace: Disables the anomaly detection feature. When set to true, the system doesn't detect anomalies in Discovery schedules.
Warning: Turning off this feature significantly impacts the Discovery experience across multiple pages, charts, and tables. |
| sn_disco_workspace.discovery_schedule_anomaly_detection_method | Discovery Admin Workspace: Determines the approach used for anomaly detection in Discovery schedules. The machine learning (ML)-based approach uses historical scan data and AI algorithms to detect anomalies and outliers. The Stats-based approach uses historical scan data and
statistical standard deviation metrics to detect anomalies and outliers.
|
| sn_disco_workspace.discovery_schedule_anomaly_discover_type | Discovery Admin Workspace: Determines the type of Discovery schedules for which anomaly detection is enabled, IP-based (CIs) and/or Cloud Discovery (Cloud Resources). To disable anomaly detection for a specific type of discovery,
excaustralialude it from the value. For example, remove "Cloud Resources" from the string if you only want to detect anomalies for IP-based Discovery schedules.
|
| sn_disco_workspace.discovery_schedule_anomaly_ml_model_sensitivity | Discovery Admin Workspace: Adjusts the sensitivity for ML-based Discovery schedule anomaly detection. Changing the sensitivity can impact detection accuracy. Lower sensitivity results in more anomalies reported, which could increase false positives. Higher
sensitivity results in fewer anomalies reported, which could increase false negatives.
|
| sn_disco_workspace.discovery_schedule_cis_discovered_anomaly_threshold | Discovery Admin Workspace: Sets the threshold percentage for detecting anomalies in the number of configuration items (CIs) discovered during a Discovery schedule execution. A Discovery status is marked as anomalous if the CI count decreases from the average by more than this threshold.
|
| sn_disco_workspace.discovery_schedule_error_anomaly_threshold | Discovery Admin Workspace: Sets the threshold percentage for detecting anomalies in Discovery schedule error counts. A Discovery status is marked as anomalous if the total error count deviates from the average error count by more than this threshold.
|
| sn_disco_workspace.discovery_schedule_runtime_anomaly_threshold | Discovery Admin Workspace: Sets the threshold percentage for detecting anomalies in Discovery schedule execution time. A Discovery status is marked anomalous if the run time deviates from the average run time of the schedule by more than this threshold.
|
| sn_disco_workspace.discovery_stats_time_scale | Discovery Admin Workspace: Configures the time scale for all relevant charts in Discovery Admin Workspace. Setting the time scale enables you to view the health of your Discovery schedules over your preferred time span.
|
|
sn_disco_workspace.enable_auto_create_schedules |
Discovery Admin Workspace: Enables automatic creation and management of Discovery schedules based on IPv6 network infrastructure data in IPAM. When set to true, Discovery uses your IPAM data to generate schedules that target IPv6 networks without requiring manual schedule configuration.
|
| sn_disco_workspace.visibility_diagnostic_utility.enabled | Discovery Admin Workspace: Enables a Virtual Agent to retrieve diagnostic information for troubleshooting issues with Discovery. Setting this property to true displays a Virtual Agent on the Diagnostics page.
|