Custom Discovery identifiers and identity probes

In addition to default ServiceNow identity probes and identifiers, you can create your own probe/sensor pairs and matching identifiers when needed.

The default ServiceNow identity probes and identifiers are configured to work together to identify discovered devices in most networks. You are encouraged to use these records whenever possible. If you need different data to identify devices, create your own probe/sensor pairs and matching identifiers to suit your particular situation.
Warning: Do not modify, disable, or delete existing ServiceNow records. If you do so, they cannot be upgraded or recovered. The best practice is to use the existing records as templates for your own elements, and then replace the ServiceNow probes, sensors, and identifiers with your custom versions in all modules where they are used (classification records, probe and sensor records, and identifiers).
All new instances use identifiers from the CMDB Identification and Reconciliation framework. Upgrades from pre-Geneva versions still preserve the legacy identifiers, but you can switch to the new identifiers using a property: glide.discovery.use_cmdb_identifiers. If you upgraded from a pre-Geneva version, you must manually add this property and set it to true to use the new identifiers. If you upgraded from Geneva or later releases, this property is available in the System Properties [sys_properties] table. To preserve functionality in custom legacy identifiers, convert them to the new CMDB identifier rules format before enabling this property. The system does not reconfigure your custom identifiers to the new framework automatically.
Note: When Service Mapping is active, the new identifiers from the CMDB Identification and Reconciliation framework are always used regardless of the property value.