The Zurich release has arrived! Interested in new features and functionalities? Click here for more

CMDB Ingestion of Configuration Item that have Duplicate Serial Numbers and Names

hcallen
Tera Contributor

3 weeks ago - last edited 3 weeks ago

We have an ask to start ingesting some CIs into the Computer class that have duplicate serial numbers and names in the source data. The source data cannot be cleaned up. The only unique identifier in the source is a Device ID that will be mapped to Correlation ID of the class. We have many other sources that ingest into the Computer class that have serial number and/or name as their unique identifier.

 

I would think if we added a new identification rule for Correlation ID that has priority over name and serial number would mitigate this issue. Is my understanding of identification rules correct?

 

Any insight on this problem would be appreciated.

 

 

0 Helpfuls
  • 438 Views
2 REPLIES 2

Cindy Trieu
ServiceNow Employee
ServiceNow Employee

2 weeks ago

Hi hcallen,

 

Before you change your rules, you will have to close any de-duplication task that contains these CI's.

 

If you truly believe that adding a new identifier entry for Correlation ID with higher priority will fix the problem, then make sure correlation ID is *always* sent in every payload for that particular source/ingestion that you send to IRE, or the same problem will occur where IRE will find duplicates based off the name and/or serial number.

 

You can work with professional services/customer success as well to help guide you through this process, but if it is as you say that correlation ID is the unique identifier for your CMDB, then in theory, it would work, yes.

 

Of course, try it on a test or subprod instance first!