How to populate discovery source value correctly for service graph connector or jamf?

[Prasnajeet1]

I have activated the service graph connector for jamf and able to populated 3036 record . however for 201 record the discovery source is populating as sg-jamf which is correct but for rest of 2800 record discovery value was populating as Technopedia-TADA4D which is wrong. Technopedia-TADA4D is a another integration in the infrastructure. So if anyone can help with solution like what to implement or how to implement would be great help me for me.

Thanks for your support in advance.

[Anshu_Anand_]

I see the screenshot and yes this issue i have faced some time ago.

In that case you have to create a reconciliation rule.

https://docs.servicenow.com/bundle/rome-servicenow-platform/page/product/configuration-management/re...

Hope Technopedia-TADA4D integration and your other data sources passes via IRE when coming to CMDB just like OOTB servicenow discovery.

Only in that case this will work. 

IRE complete working :-

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0750386

Else If you are using some transform map script for Technopedia-TADA4D you have to define a logic in the script that data passes via IRE. you can also use IntegrationHUB ETL for cmdb

Script for IRE execution

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0750383

Now coming to creation of reconciliation rule,

In ci class manager goto the computer class

Add reconciliation rule there

It asks for discovery source and priority.

You can add multiple rules.

The highest the priority 1 given to data source, that will take the priority of updating the CIs

The lower rank 2 will update when 1st priority attributes are stale for some time.

Now create data refresh rule. define number of days for the datasource which you dont want to be touched via other data sources.

Example:-

Priority 1:- sg-jamf

attributes:- ip address, os domain,serial number..........

Priority 2:-Technopedia-TADA4D

attributes:- ip address, os domain,serial number............

data refresh rule:-

1. discovery source:- sg-jamf

effective duration :- 100 days

Now first sg-jamf runs, it will populate the CIs.

next run the Technopedia-TADA4D, it will not update the CIs attribute commonly defined in both priority until 100 days if only sg-jamf ci becomes stale .

The data refresh and reconciliation works via cmdb_datasource_last_update table.

it stores which CI attribute was when last updated via which source.

You can increase number of days as you want.

If it helps, please mark my answer as correct

[Prasnajeet1]

Hi Anshu

Thanks for your response. I have created the reconciliation rule and as well data refresh rule. Execute the scheduled import. However there is no luck. Existing record are not getting updated as discovery source SG-jamf. I deleted those and again run the scheduled import. Now all my record updated as expected. But again when casper integration execute it changed discovery source value.  Also there is a another if create the reconciliation on the cmdb_ci_computer table it will impact other integration like InTUne and SCCM as well.

Could you please suggest me how I should write the reconciliation so that it will not impact other integration and I can achieve my requirement as well.

[Prasnajeet1]

is it possible to stop the casper data source to update the discovery source field?

[Anshu_Anand_]

If its coming via IRE and not via simple transform map,

Mention it in the reconciliation rule as last priority.

Also Mention the data source field as attribute 

[Prasnajeet1]

Anshu  one more point i would like to highlight here.

Once the casper integration update discover source field as "casper" after that when I run the jamf integration it is not updating the discovery source field as jamf.  It as always like casper only.

Jamf is used robust transform map right. Can we do something in the robust transform map itself to update discovery source as jamf.

Or is it possible if i write a fix script and modified discovery soruce field value  all the record from "casper" to "sg-jamf" and then I will write another BR to to stop casper integration to update the discovery source.