IRE and RTE incorrectly matching CMDB item

[Michael George]

I've got a custom ETL transform map setup and I thought it was all working correctly, but I found out today that it is matching some items in the IRE that it shouldn't be. I was fairly sure that the identification rule for "Hardware" was my problem as that includes a match against the "name" column, but even after creating a new rule on "Computer" (it's worth noting that I'm using the cmdb_ci_handheld_computing class here) that does NOT include a name match, I'm still not getting a new device created when I think I should.

 

The identification rule for Handheld Computing:

The ETL data preview of my json data:

The mapping to the class in ETL:

Finally, what my activity stream looks like when it imports two records in an import set:

 

It looks like it is importing the first record, matching an existing record on something, then bringing in the second record and matching on the same thing that sure doesn't appear to be serial number or mac address.

Any insights or things to check on would be appreciated.

[Rafał Rataj]

any updates perhaps?

have the same issue with Service Graph Connector for Meraki
I see the payload coming correctly for IP switches and then 6 of them are mapped to the same CI .. 

already on level of Sources [sys_object_source], then Serial Numbers 

and as they are mapped to 1 CI then I have only 1 CI for all those incoming devices  
 

[Martin Grosskop]

You might want to check what is happening on your Sources table (sys_object_source).

Assume there was an initial issue with your identification rules, which resulted in multiple input records mapping to one CI.

Then let us assume you spotted the issue with your rules and fixed your identification rules.

Then when you re-run the IH-ETL, note that Source takes precedence over all other IRE rules.

So once a given Source is bound to a given CI, then that link takes precedence.

You should delete the source records to "break" the link.

Then run your IH-ETL again, and this will give the identification rules a chance to do their job.

Not saying this is your issue, but this is something I come across from time to time.