How to validate Reconciliation Engine configuration

Go to solution
RahulY00040
Tera Contributor

3 weeks ago

Hello everyone,

We have multiple data sources populating Hardware CIs and their child CIs in the CMDB. For each source, we have configured Reconciliation Definitions, some with unique priorities and others sharing the same priority level.

We would now like to validate each Reconciliation Definition against its corresponding data source and the CIs currently present in the CMDB.

Could you please advise on:

  • How to perform this validation effectively?
  • Which tables should be referenced when validating IRE behavior using the createOrUpdateCIEnhanced() API?
  • What is the significance of the cmdb_datasource_last_update table in this context?

Thanks in advance,
Rahul

0 Helpfuls
  • 950 Views
1 ACCEPTED SOLUTION

Go to solution
fknell
Tera Patron
In response to RahulY00040

3 weeks ago - last edited 3 weeks ago

Hi @RahulY00040,

With the following script, you can insert the generated payload as outlined in the previous post to the CMDB and trigger both Identification and Reconciliation Rules. You only need to set the discovery source according to your environment. The records will be visible in the multi source table as well, once you enabled the feature.

 

Please make sure to do this in sub-prod systems only.

 

I also updated the initial post based on your feedback. Thank you for bringing this topic up. This is option 1 from the examples of how to reuse the mock data. 

 

var payload = {
   "items": [],
   "relations": []
}

var jsonUtil = new JSON();
var input = jsonUtil.encode(payload);
var output = SNC.IdentificationEngineScriptableApi.createOrUpdateCI('SOURCE', input);
gs.print(output);

 

Hope this helps!

View solution in original post

5 REPLIES 5

Go to solution
RahulY00040
Tera Contributor

2 weeks ago

I was able to validate it further by triggering multiple calls to IRE from background script and documented reconciliation design/implementation works as defined. If data from this table-cmdb_datasource_last_update gets deleted, then IRE does not have any details about who updated what and upcoming payload even from less priority source will be taken into account.

 

I was able to validate it.

0 Helpfuls