Properties for Identification and Reconciliation
Use the Identification and Reconciliation properties to configure the identification and reconciliation engine (IRE).
These properties are available for Identification and Reconciliation. To view and edit these properties, the sn_cmdb_admin or admin role is required.
Note: To open the System Properties [sys_properties] table, enter sys_properties.list in the navigation filter.
| Property | Description |
|---|---|
| Enforce the requirement that required attributes cannot be null during identification and reconciliation. glide.required.attribute.enabled |
|
| Allow class upgrade during IRE identification and reconciliation. glide.class.upgrade.enabled |
When false, IRE rejects a payload (or a payload item in Enhanced IRE) with the respective reclassification update, and creates a reclassification task. |
| Allow class downgrades during IRE identification and reconciliation. glide.class.downgrade.enabled |
When false, IRE rejects a payload (or a payload item in Enhanced IRE) with the respective reclassification update, and creates a reclassification task. |
| Allow class switching during IRE identification and reconciliation. glide.class.switch.enabled |
When false, IRE rejects a payload (or a payload item in Enhanced IRE) with the respective reclassification update, and creates a reclassification task. |
| glide.identification\_engine.update\_without\_upgrade\_enabled | Enable IRE to process CI updates with upgrade reclassification updates. This property takes precedence over the glide.class.upgrade.enabled property.
Depending on the property setting, IRE processes or skips the upgrade update:
|
| glide.identification\_engine.update\_without\_downgrade\_enabled | Enable IRE to process CI updates with downgrade reclassification updates. This property takes precedence over the glide.class.downgrade.enabled property.
Depending on the property setting, IRE processes or skips the downgrade update:
|
| glide.identification\_engine.update\_without\_switch\_enabled | Enable IRE to process CI updates with switch reclassification updates. This property takes precedence over the glide.class.switch.enabled property.
Depending on the property setting, IRE processes or skips the switch update:
|
| glide.identification\_engine.reclassification\_restriction\_rules\_enabled | Globally enable or disable the application of active reclassification restriction rules.
|
| Allow the update of an empty field by a lower priority data source. glide.reconciliation.override.null |
|
| Controls how identification processes a small set of duplicate CIs. glide.identification\_engine.skip\_duplicates |
If the number of duplicate CIs is less than the threshold specified by glide.identification_engine.skip_duplicates.threshold, then the oldest of the duplicate CIs is picked as a match and gets updated. That oldest CI is also designated as the main CI for that set of duplicate CIs. For the rest of the duplicate CIs, the duplicate_of field is set as a reference to the main CI.
Matching a CI fails, and an error is logged.
|
Maximum number of CIs that can be in a set of duplicate CIs to allow identification to process the duplicate CIs according to the setting of glide.identification_engine.skip_duplicates. glide.identification_engine.skip_duplicates.threshold | If the number of duplicate CIs exceeds the threshold, then identification processes the duplicate CIs as if glide.identification_engine.skip_duplicates is set to false.
|
Maximum number of log runs that can be displayed when navigating to Configuration > Identification Logs. glide.identification_logs.max_run_ids |
|
| glide.cache.size.service\_cache | Maximum cache size (in MB) that is used by the identification engine for inbound and outbound relations. When the limit is reached, the least recently used cached data is discarded, releasing space for new data.Note: You cannot disable the service cache.
|
| glide.identification\_engine.granular\_insert\_locking | Determines whether to use multiple granular insert locks or single global insert lock. Set to false if there are performance issues associated with the usage of multiple granular insert locks.
|
| glide.identification\_engine.batch\_update\_last\_discovered | Controls batch update of last_discovered field in CIs that are being processed by the identification engine. Set to false if there are business rules that apply to the last_discovered field, and you want to trigger these rules when calling an Identification and Reconciliation API.
|
| glide.identification\_engine.related\_items\_local\_cache\_count | For optimization, a custom number of locally cached query result entries of related/lookup items.
Note: If there is a memory issue due to optimization related to using local cache, set the glide.identification_engine.related_items_local_cache_count and the glide.identification_engine.dependent_items_local_cache_count properties to 0. |
| glide.identification\_engine.dependent\_items\_local\_cache\_count | For optimization, a custom number of locally cached query result entries of dependent CIs.
Note: If there is a memory issue due to optimization related to using local cache, set the glide.identification_engine.related_items_local_cache_count and the glide.identification_engine.dependent_items_local_cache_count properties to 0. |
| glide.identification\_engine.independent\_items\_local\_cache\_count | For optimization, a custom number of locally cached query result entries of independent CIs.
Setting the value to 0 avoids using local cache for independent CIs which might affect performance. |
| glide.cmdb.logger.source.identification\_engine | Enable and configure what type of details the system logs when using IRE outside the scope of identification simulation. For example, when using an API, ECC queue or scheduled jobs.
Note: Depending on the setting, the system can generate large amounts of data that might affect overall system performance. Set the value with caution, and limit the level of details and use time to the minimum necessary for testing or debugging. For more troubleshooting information, see the How to capture IRE [identification and reconciliation engine] debug logs [KB0750382] knowledge base article. |
| glide.identification\_engine.partial\_payload\_items\_max\_size | Maximum number of items allowed when creating a partial payload. When that limit is reached, the partial payload is split. For example, when IRE creates a partial payload, items and associated relations and references, are all merged in one partial payload. This merge could result in a large partial payload. Adjusting this property can help with performance issues related to IRE processing of partial items.
|
| glide.identification\_engine.partial\_items\_process\_limit | Maximum number of partial items to be fetched in a single IRE call. After reaching this limit, IRE fetches only partial items corresponding to complete items in the input payload. Adjusting the value can help with performance issues related to IRE processing of partial items.
|
| glide.identification\_engine.partial\_items\_process\_absolute\_limit | Absolute limit of the number of partial items for IRE to fetch, after which, IRE stops fetching partial payloads from the CMDB IRE Partial Payloads [cmdb_ire_partial_payloads] table. Adjusting the value can help with performance issues related to IRE processing of partial items.
|
| glide.identification\_engine.skip\_updating\_source\_last\_discovered\_if\_older | Determines how IRE updates the last_discovered and the discovery_source attributes in the CMDB.
Note: Only the attributes mentioned above are affected by this property in an update operation.
|
| glide.identification\_engine.ire\_message\_listener\_skip\_updating\_source\_last\_discovered\_to\_now | If Robust Transform Engine (RTE) does not pass the ire.skip_updating_last_scan_to_now custom property on the Robust Import Set Transformer form, IRE uses the value of this property for the skip_updating_source_last_discovered_to_now IRE option.
|
| glide.identification\_engine.skip\_updating\_last\_scan\_if\_older | Determines how IRE uses the source_recency_timestamp value in a payload to determine whether to update the last_scan attribute in the Source [sys_object_source] table.
You can check the input payload for a CI and the last_scan attribute value in the Source [sys_object_source] table to learn if IRE will update that last_scan value or not. Note: Only the attributes mentioned above are affected by this property in an update operation.
|
| glide.identification\_engine.ire\_message\_listener\_skip\_updating\_last\_scan\_to\_now | If RTE does not pass the ire.skip_updating_last_scan_to_now custom property on the Robust Import Set Transformer form, IRE uses the value of this property for the ire.skip_updating_last_scan_to_now IRE option.
|
| glide.identification\_engine.platform\_domain\_separation\_enabled | Toggles domain separation support mode during IRE processing.
|
| glide.identification\_engine.enable\_identifier\_optional\_condition | Enables advanced options for regular identifier entries in identification rules. Those advanced options let you add conditions to narrow the set of records that will be searched for a matching CI. Note: This property affects only regular identifier entries (it doesn't affect lookup or hybrid identifier entries). In the base system, identifier entries of various classes are pre-configured with advanced options conditions. All these pre-configured conditions in regular identifier entries will automatically apply when you set this property to true. To prevent unexpected behavior, review those predefined conditions in regular identifier entries before setting this property to true. In the Filter box in the primary navigation, enter
|
| glide.identification\_engine.enable\_reconciliation\_filter\_before\_update | Determines whether filter conditions of a reconciliation rule are applied before a value change during payload processing, or after.
|
| glide.identification\_engine.skip\_sys\_object\_source\_matching | Determines whether IRE identification processes have the priority in being used to uniquely identify CIs in a payload, over the use of sys_object_source lookup. When set to true, the system prioritizes sending any payload that contains a criterion attribute to be processed by IRE identification instead of using sys_object_source lookup. This can be useful in situation that can potentially generate duplicate CIs. For example, using sources in which identifying attributes are changing while the source native key isn't. However, when source_native_key is the only identifiable attribute (for example, if none of the identification rules can run because attributes and values for rule identifiers aren't present in the payload), then source_native_key is used for identification even when the property is set to true.
|
| glide.identification\_engine.lookup\_match.create\_duplicate\_task\_ci.enabled | Enables IRE behavior of creating de-duplication tasks for duplicate related items in a lookup table detected during a lookup-based identification. Set the property to reflect on whether such duplication is valid in the organization and doesn't require remediation, or isn't valid and the duplication should be remediated.
|
| glide.identification\_engine.dynamic\_ire\_enabled | Switch between using Dynamic IRE or Static IRE. Set to 'true' to use Dynamic IRE and to turn off Static IRE.
|
| glide.identification\_engine.dynamic\_ire.auto\_compare | Enables comparison between the processing outputs of Dynamic IRE and Static IRE for all payloads. - Type: true \| false - Default: true - Learn more: Dynamic IRE - Location: System Properties \[sys\_properties\] table |
| glide.identification\_engine.non\_dependency\_relation.duplicate\_detection | Set IRE behavior when the payload contains duplicate non-dependent relationships (identical parent/child relationship type). When set to true, IRE detects duplicate non-dependent relationships in a payload. When set to false, IRE doesn't detect duplicate non-dependent relationships in a payload.
|