Tanium IT Asset to CI CMDB integration using SG-Tanium Out of box connector

[jayzee08]

Good day all, 

I was hoping to find some assistance on a problem we are having with our Tanium IT Asset Mgmt Graph connector.  It is completely out of the box using the Guided Support.  We are getting all our CIs and classes appropriately, however we are receiving about a 10% duplication of CI's where the Serial number is duplication but the NAME is not, due to it being re-purposed or provisioned.  They will usually have a different Last updated date, but will be the only differentiation.  

Any thoughts on how to eliminate them from being included in the import?  Deleted them daily from Tanium is a very manual process.  

Changing the graph connector is rough b/c it's OOB- and we don't really want to tinker with it.

So any other ideas - let me know.

[AJ-TechTrek]

HI @jayzee08 ,

Please use the Integration ETL hub to check the unique or correlation ID to found which is using to update or create the record.

below article which help you alot in this.

https://www.servicenow.com/community/cmdb-articles/tanium-service-graph-connector/ta-p/2754467

https://developer.tanium.com/site/global/docs/how_tos/servicenow/index.gsp

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

Thanks

AJ

Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/

ServiceNow Community Rising Star 2024

[Ashok Sasidhara]

You need to list down the CI classes where the duplicates are getting created. Then go to CI class manager, open each of those CI classes and click on 'Identification rules' tab to review the identifier entries for each class. Comparison of current identifier entries for each class with the attributes in the source data from tanium for each class should ideally help to identify what changes are needed in the identifier entries to reduce the number of duplicates created. In short, setting the best possible identifier entries is the solution to reduce the probability of duplication. 

[William44]

This sounds like the Service Graph connector is performing as expected. The Service Graph connector uses the IRE to identify CIs, the OOB hardware rule checks the following attributes to determine if the CI already exists, or is new:

1. Product Instance Identifier on the Hardware table
2. Serial Number and Serial Number Type on the Serial Number table
3. Serial Number on the Hardware table
4. Name on the Hardware table
5. MAC Address and Name on the Network Adapter table

If any of the above attributes for the discovery match any existing entries in the CMDB, the CI exists in the CMDB, and will be updated.  It sounds like you are seeing the Serial Number match (you can check the Discovery Status Logs for details on what attributes satisfied the match conditions.

If you want to have different CIs created for the same hardware (serial number) when it has a new name, you can update the Identification Rules in the Class Manager.