Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Detecting duplicate CIs

Log in to subscribe to topics and get notified when content changes.

Detecting duplicate CIs

When the identification process encounters duplicate CIs, it groups each set of duplicate CIs into a de-duplication task for review and remediation. A large number of duplicate CIs might be due to weak identification rules. You can configure the identification engine to reconcile duplicate CIs.

During CMDB Identification, processing of duplicate CIs is determined by the properties glide.identification_engine.skip_duplicates (set to true by default) and glide.identification_engine.skip_duplicates.threshold (set to 5 by default), and on the number of duplicate CIs that are detected. You can configure these properties so duplicate CIs are automatically reconciled, skipping duplication.

  • If glide.identification_engine.skip_duplicates is true, and 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. The rest of the duplicate CIs are tagged as duplicates by setting the cmdb_ci's discovery_source field as 'Duplicate'. During matching, the identification engine filters out any CIs in which state discovery_source=Duplicate.
  • If glide.identification_engine.skip_duplicates is false, then matching of duplicate CIs fails with an error, and none of the duplicate CIs are updated.
Note: In either case, de-duplication tasks are always created.

To modify these properties, first add them to the System Properties [sys_properties] table. For more information, see Components installed with Identification and Reconciliation.

Review de-duplication tasks

For information about reviewing and remediating de-duplicate tasks, see Duplicate CIs.