Home New York IT Operations Management IT Operations Management ITOM Visibility Discovery Discovery configuration Discovery properties

Discovery properties

Discovery properties allow you to control several aspects of the horizontal discovery process.

Navigate to Discovery Definition > Properties to edit these properties:

IP properties


Field	Description
glide.discovery.assigned_user_match_field	Help the Help Desk attempts to match a Windows user name it finds with the the user_name field of the User [sys_user] table. This field in the sys_user table is used to associate a computer CI with a user and enables you to select an alternative field for matching. For example, you can create a field called u_username, and then populate it with a user ID that can be matched against the Windows user name. In this case, replace the default value in the property with u_username.
glide.discovery.enforce_ip_sync	Enforce syncing of IP addresses: This sets the first IP address. Each time a computer with multiple NICs is discovered, one of the IP addresses associated with the NICs is chosen as the IP Address field of the CI. A value of false collects all NIC IP addresses. Type : true \| false Default value: true
glide.discovery.exclude_ip_sync_classes	Defines CI classes whose IP addresses should not be substituted if the address returned by Discovery does not 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. Type : string Default value: cmdb_ci_lb

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 disabled 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). Type : true \| false Default value: true
glide.discovery.debug.network_discovery	Network discovery debugging: Enables extensive logging of all Network Discovery activities on the instance. Type : true \| false Default value: true Learn More: Discovery monitoring and issue resolution
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. Type : integer Default value: 28
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: First Router: the first router that discovers the network is associated Last Router: the last router that discovers the network is associated Most Networks: the router with the most attached networks is associated Least Networks: the router with the least attached networks is associated Type : choice list Default value: Most Networks Additional options: First Router, Last Router, Least Networks
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. Type : string Default value: 6,117,9,71,209
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". Type : string Default value: 7,8,9,26,53,62,69,71,78,115,117,209

Other Discovery properties


Field	Description
com.snc.use_external_credentials	Allows the use of external storage of credentials. Type: true \| false Default value: true
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. Type : true \| false Default value: false
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. Type: integer Default value: 3600
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 a absolute path to the directory. Type: true \| false Default value: false
glide.discovery.adme.base_dir_windows	ADME - Windows Base Dir: A network share on the target Windows machines to be used as a workspace. Type: string Default value: admin$\temp
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 amount of samples are taken. Type: integer Default value: 100
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 will be kept. Type: integer Default value: 24
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. Type: integer Default value: 120
glide.discovery.application_mapping	Application mapping: Enable the application mapping portion of Discovery Attention: Disabling this property disables the creation of relationships between applications but does not disable the ADM probes and sensors, nor does it prevent process classification. Type : true \| false Default value: true Learn More: Application Dependency Mapping (ADM) for Discovery
glide.discovery.debug.ci_identification	CI identification debugging: If set to true, enables debug logging (into the CI Identification Log) for CI Identification. Type : true \| false Default value: false
glide.discovery.discover_aws_ec2_host_metadata	When doing IP-based discovery against a given host, also run probes that retrieve AWS EC2 metadata. Type : true \| false Default value: true
glide.discovery.discover_azure_host_metadata	When doing IP-based discovery against a given host, also run probes that retrieve Azure metadata. Type : true \| false Default value: true
glide.discovery.discover_software	Discover software packages: Enable the discovery of software packages. Type : true \| false Default value: true Learn More: General software package discovery
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 is set by WMI. Type : true \| false Default value: true
glide.discovery.enable_adme	ADME: Enable enhanced ADM probe. If set to true, the ADM Enhanced probe will be triggered and only fall back to the ADM probe as needed. Type: true \| false Default value: false
glide.discovery.enable_file_tracking	Enable configuration file tracking as part of the Pattern based Horizontal Discovery. If set to true, the system allows you to specify paths of configuration files for applications that are discovered by patterns. You can track and compare tracked configuration files. Type: true \| false Default value: true
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 does not stop processing other IP addresses. Type: true \| false Default value: false 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. Type: true \| false Default value: true
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 disabled, stores the IP address for each device. Type : true \| false Default value: false
glide.discovery.file_tracking.max_file_size	File Tracking: The maximum file size for tracked configuration file content. Type: integer Default value: 500000
glide.discovery.file_tracking.max_files_per_ci	File Tracking: The maximum number of tracked configuration files per CI. Type: integer Default value: 50
glide.discovery.file_tracking.change_limit_count	File Tracking: Number of changes allowed on a tracked configuration file in the defined time window. Type: integer Default value: 4
glide.discovery.file_tracking.change_limit_days	File Tracking: Time window (in days) that limits the number of changes on a tracked configuration file. Type: integer Default value: 7
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. Type : string Default value: ^([^.]+)\.((?:[^.]+\.)+[^.]+)$
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. Type : true \| false Default value: true
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. Type : choice list Default value: Lower case Additional options: Upper case, No change
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. Type : true \| false Default value: true
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". Type : true \| false Default value: false
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. Type : true \| false Default value: false
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. Type : true \| false Default value: false
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. Type : true \| false Default value: false
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. Type : true \| false Default value: false Learn More: Check IP service affinity for Discovery and Orchestration
glide.discovery.L3_mapping	Map servers and network devices to routers and layer-3 switches If the "L3 mapping" property is enabled, it will map servers and network gears to its associated routers and layer-3 switches. Type : true \| false Default value: true Learn More: Network discovery
glide.discovery.log_message_length	Log Message Length: Limit the maximum message length that is displayed in Discovery Log table. A value of 0 or any negative number disables this limit. Type : integer Default value: 200 Learn More: Logs for Discovery
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 cancelled. The default value is 3. A value of 0 or any negative number disables this restriction. Type : integer Default value: 3
glide.discovery.network_discovery.functionality	Networks discovery functionality: the Functionality used to discover networks. Usually this should be SNMP only. Type : string Default value: SNMP only
glide.discovery.perf.metrics.enable_collection	Whether or not to collect Discovery performance metrics. Type: true \| false Default value: true
glide.discovery.perf.metrics.rollup_by_build	Whether or not to aggregate individual Discovery performance metrics into a roll-up table that groups by discovery build. Type: true \| false Default value: true
glide.discovery.perf.metrics.rollup_by_status	Whether or not to aggregate individual Discovery performance metrics into a roll-up table that groups by discovery status. Type: true \| false Default value: true
glide.discovery.perf.metrics.rollup_by_target	Whether or not to aggregate individual Discovery performance metrics into a roll-up table that groups by target IP address. Type: true \| false Default value: true
glide.discovery.populate_software_instance_table	If set to true, Discovery populates these tables for software discovery: `cmdb_software_instance` `cmdb_sam_sw_install` Type: true \| false Default value: false Use this property only if you were using Software Asset Management with Discovery in pre-Jakarta releases and want to keep populating the `cmdb_software_instance` table. 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. Type : integer Default value: 1
glide.discovery.roundingInterval.ram	Memory rounding: Enter the number to round the computer RAM to. The units are in MB. Type : integer Default value: 1
glide.discovery.sensors.fire_ssh_probe	In case the VIPs (Load Balancer Virtual Services) did not 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. Type : true \| false Default value: true
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. Type : true \| false Default value: true
glide.discovery.shazzam_ranges_json	Use JSON for IP ranges in Shazzam: If set to true, discovery will encode Shazzam's IP ranges as JSON, dramatically reducing the payload size. Type : true \| false Default value: true
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 will be filtered out. Type: string Default value: Language Pack, Hotfix Security Update
glide.discovery.software_sccm_managed	Windows software is SCCM managed: If set to true, Discovery will not populate software for computer CIs also managed by SCCM. Type : true \| false Default value: false Learn More: Discovery and SCCM together
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. Type: true \| false Default value: true
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 need to be processed by a sensor. It only needs to be processed if the results have changed from the last discovery run. Type : true \| false Default value: false Learn More: Create or modify a probe Note: In previous releases, this property was true by default. The value in this property is not 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. Type : integer Default value: 53
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. Type : true \| false Default value: false
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. Type: true \| false Default value: false Navigate to System Properties > All Properties 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. Type: integer Default value: 4
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. Type: integer Default value: 30
glide.eccprobe.max_queued_probes_per_run	Set the maximum number of probes a node can pick up during a run. Type: integer Default value: 20
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. Type: string Default value: NODE_AGENT

Previous topic

Next topic

Release version

Discovery properties

Discovery properties allow you to control several aspects of the horizontal discovery process.

Navigate to Discovery Definition > Properties to edit these properties:

IP properties


Field	Description
glide.discovery.assigned_user_match_field	Help the Help Desk attempts to match a Windows user name it finds with the the user_name field of the User [sys_user] table. This field in the sys_user table is used to associate a computer CI with a user and enables you to select an alternative field for matching. For example, you can create a field called u_username, and then populate it with a user ID that can be matched against the Windows user name. In this case, replace the default value in the property with u_username.
glide.discovery.enforce_ip_sync	Enforce syncing of IP addresses: This sets the first IP address. Each time a computer with multiple NICs is discovered, one of the IP addresses associated with the NICs is chosen as the IP Address field of the CI. A value of false collects all NIC IP addresses. Type : true \| false Default value: true
glide.discovery.exclude_ip_sync_classes	Defines CI classes whose IP addresses should not be substituted if the address returned by Discovery does not 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. Type : string Default value: cmdb_ci_lb

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 disabled 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). Type : true \| false Default value: true
glide.discovery.debug.network_discovery	Network discovery debugging: Enables extensive logging of all Network Discovery activities on the instance. Type : true \| false Default value: true Learn More: Discovery monitoring and issue resolution
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. Type : integer Default value: 28
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: First Router: the first router that discovers the network is associated Last Router: the last router that discovers the network is associated Most Networks: the router with the most attached networks is associated Least Networks: the router with the least attached networks is associated Type : choice list Default value: Most Networks Additional options: First Router, Last Router, Least Networks
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. Type : string Default value: 6,117,9,71,209
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". Type : string Default value: 7,8,9,26,53,62,69,71,78,115,117,209

Other Discovery properties


Field	Description
com.snc.use_external_credentials	Allows the use of external storage of credentials. Type: true \| false Default value: true
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. Type : true \| false Default value: false
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. Type: integer Default value: 3600
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 a absolute path to the directory. Type: true \| false Default value: false
glide.discovery.adme.base_dir_windows	ADME - Windows Base Dir: A network share on the target Windows machines to be used as a workspace. Type: string Default value: admin$\temp
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 amount of samples are taken. Type: integer Default value: 100
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 will be kept. Type: integer Default value: 24
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. Type: integer Default value: 120
glide.discovery.application_mapping	Application mapping: Enable the application mapping portion of Discovery Attention: Disabling this property disables the creation of relationships between applications but does not disable the ADM probes and sensors, nor does it prevent process classification. Type : true \| false Default value: true Learn More: Application Dependency Mapping (ADM) for Discovery
glide.discovery.debug.ci_identification	CI identification debugging: If set to true, enables debug logging (into the CI Identification Log) for CI Identification. Type : true \| false Default value: false
glide.discovery.discover_aws_ec2_host_metadata	When doing IP-based discovery against a given host, also run probes that retrieve AWS EC2 metadata. Type : true \| false Default value: true
glide.discovery.discover_azure_host_metadata	When doing IP-based discovery against a given host, also run probes that retrieve Azure metadata. Type : true \| false Default value: true
glide.discovery.discover_software	Discover software packages: Enable the discovery of software packages. Type : true \| false Default value: true Learn More: General software package discovery
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 is set by WMI. Type : true \| false Default value: true
glide.discovery.enable_adme	ADME: Enable enhanced ADM probe. If set to true, the ADM Enhanced probe will be triggered and only fall back to the ADM probe as needed. Type: true \| false Default value: false
glide.discovery.enable_file_tracking	Enable configuration file tracking as part of the Pattern based Horizontal Discovery. If set to true, the system allows you to specify paths of configuration files for applications that are discovered by patterns. You can track and compare tracked configuration files. Type: true \| false Default value: true
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 does not stop processing other IP addresses. Type: true \| false Default value: false 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. Type: true \| false Default value: true
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 disabled, stores the IP address for each device. Type : true \| false Default value: false
glide.discovery.file_tracking.max_file_size	File Tracking: The maximum file size for tracked configuration file content. Type: integer Default value: 500000
glide.discovery.file_tracking.max_files_per_ci	File Tracking: The maximum number of tracked configuration files per CI. Type: integer Default value: 50
glide.discovery.file_tracking.change_limit_count	File Tracking: Number of changes allowed on a tracked configuration file in the defined time window. Type: integer Default value: 4
glide.discovery.file_tracking.change_limit_days	File Tracking: Time window (in days) that limits the number of changes on a tracked configuration file. Type: integer Default value: 7
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. Type : string Default value: ^([^.]+)\.((?:[^.]+\.)+[^.]+)$
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. Type : true \| false Default value: true
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. Type : choice list Default value: Lower case Additional options: Upper case, No change
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. Type : true \| false Default value: true
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". Type : true \| false Default value: false
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. Type : true \| false Default value: false
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. Type : true \| false Default value: false
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. Type : true \| false Default value: false
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. Type : true \| false Default value: false Learn More: Check IP service affinity for Discovery and Orchestration
glide.discovery.L3_mapping	Map servers and network devices to routers and layer-3 switches If the "L3 mapping" property is enabled, it will map servers and network gears to its associated routers and layer-3 switches. Type : true \| false Default value: true Learn More: Network discovery
glide.discovery.log_message_length	Log Message Length: Limit the maximum message length that is displayed in Discovery Log table. A value of 0 or any negative number disables this limit. Type : integer Default value: 200 Learn More: Logs for Discovery
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 cancelled. The default value is 3. A value of 0 or any negative number disables this restriction. Type : integer Default value: 3
glide.discovery.network_discovery.functionality	Networks discovery functionality: the Functionality used to discover networks. Usually this should be SNMP only. Type : string Default value: SNMP only
glide.discovery.perf.metrics.enable_collection	Whether or not to collect Discovery performance metrics. Type: true \| false Default value: true
glide.discovery.perf.metrics.rollup_by_build	Whether or not to aggregate individual Discovery performance metrics into a roll-up table that groups by discovery build. Type: true \| false Default value: true
glide.discovery.perf.metrics.rollup_by_status	Whether or not to aggregate individual Discovery performance metrics into a roll-up table that groups by discovery status. Type: true \| false Default value: true
glide.discovery.perf.metrics.rollup_by_target	Whether or not to aggregate individual Discovery performance metrics into a roll-up table that groups by target IP address. Type: true \| false Default value: true
glide.discovery.populate_software_instance_table	If set to true, Discovery populates these tables for software discovery: `cmdb_software_instance` `cmdb_sam_sw_install` Type: true \| false Default value: false Use this property only if you were using Software Asset Management with Discovery in pre-Jakarta releases and want to keep populating the `cmdb_software_instance` table. 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. Type : integer Default value: 1
glide.discovery.roundingInterval.ram	Memory rounding: Enter the number to round the computer RAM to. The units are in MB. Type : integer Default value: 1
glide.discovery.sensors.fire_ssh_probe	In case the VIPs (Load Balancer Virtual Services) did not 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. Type : true \| false Default value: true
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. Type : true \| false Default value: true
glide.discovery.shazzam_ranges_json	Use JSON for IP ranges in Shazzam: If set to true, discovery will encode Shazzam's IP ranges as JSON, dramatically reducing the payload size. Type : true \| false Default value: true
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 will be filtered out. Type: string Default value: Language Pack, Hotfix Security Update
glide.discovery.software_sccm_managed	Windows software is SCCM managed: If set to true, Discovery will not populate software for computer CIs also managed by SCCM. Type : true \| false Default value: false Learn More: Discovery and SCCM together
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. Type: true \| false Default value: true
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 need to be processed by a sensor. It only needs to be processed if the results have changed from the last discovery run. Type : true \| false Default value: false Learn More: Create or modify a probe Note: In previous releases, this property was true by default. The value in this property is not 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. Type : integer Default value: 53
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. Type : true \| false Default value: false
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. Type: true \| false Default value: false Navigate to System Properties > All Properties 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. Type: integer Default value: 4
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. Type: integer Default value: 30
glide.eccprobe.max_queued_probes_per_run	Set the maximum number of probes a node can pick up during a run. Type: integer Default value: 20
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. Type: string Default value: NODE_AGENT

How search works:

Topics are ranked in search results by how closely they match your search terms

Discovery properties

Discovery properties

On this page

Discovery properties

Discovery properties

Log in to personalize your search results and subscribe to topics