Identification rules in CMDB and prioritization

[lmundere]

Hi,

We have got several integrations feeding our CMDB and I want to have a rule , that, when a CI is discoverable by Discovery (discovery source= servicenow), i dont want any other integration to write on the CI, I have created the following rule, and now wondering if it is correct or not. See sreenshot.

[Anshu_Anand_]

Its good but have to define data refresh rules also.

To make sure CIs discovered by servicenow can never be updated by any other data source, create a data refresh rule which is in reconciliation rules.

Define number of days for servicenow source as example 1000 days or more , so what happens, for next 1000 days no other source will update the attributes coming under servicenow discovery source.

cmdb_datasource_last_update table consists of each attribute and what updated this attribute at last time.

Mark answer as correct if its helpful

[Anshu_Anand_]

something like this @

@lmundere 

[Sandeep90]

This is correct but I would suggest going through this doc to better understand the reconciliation rules as, if there is a new rule for selected attributes it will overtake precedence over all attributes rules, ie... if there is a rule with 100 on ServiceNow with all attributes and there is a rule for Ansible with priority 200 with just RAM attribute then Ansible will be able to update RAM even though ServiceNow has priority 100.  Also, use the preview rule button on the reconciliation page to view which source will have precedence for the attributes.