Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
When discovery/Identification engine creates new CI or updates existing one - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • When discovery/Identification engine creates new CI or updates existing one
KB0727271

When discovery/Identification engine creates new CI or updates existing one


3607 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

 

Overview


How discovery identification engine works while identifying for existing Cis and takes a decision on whether to create new CI or updates the existing one.

Discovery identification matching process


Discovery tries to find if an existing entry in found in the CMDB by looking at identification rules. We will take an example of Hardware Rule:

https://<instance_name>.service-now.com/nav_to.do?uri=cmdb_identifier.do?sys_id=a1d19344c3b33100d8d4bea192d3aedc

 

The matching process occurs from top to bottom, lowest priority first.

Rule 1 is the topmost rule with serial_number and serial_number_type. 

The search will be on the cmdb_serial_number table.

There are two possibilities in this scenario:

Case 1: The discovery payload contains serial_number and serial_number_type

            In this case, the Identification engine searches the table cmdb_serial_number for the match and again it will have two more possible outcomes:

           Match found: It will ignore the other rules with priorities 200, 300 and 400 in this example and updates the respective CI.

               Identifier: Hardware Rule, Rule 1 Searched on <cmdb_serial_number> for attributes: serial_number,serial_number_type:Match.

           Match not found: It will continue with next higher order rules and continues until a match is found.

               Identifier: Hardware Rule, Rule 1 Searched on <cmdb_serial_number> for attributes: serial_number,serial_number_type:No Match.

 

Case 2: Discovery payload doesn't contain either serial_number or serial_number_type fields. 

           In this case, it will show up a message in discovery logs stating, "Skipped Identifier entry" and continues to next rule.

Identifier: Hardware Rule, Rule 1 Searched on <cmdb_serial_number> for attributes: serial_number,serial_number_type:Skipped Identifier Entry.

 

This process continues until the match is found on the tables defined in Identifier rules. If there is no match found after running all the rules, then it will create a new CI.

 

Additional Information


This youtube video provides complete information regarding the discovery identification process:

CMDB Identification and Reconciliation Framework


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.