Back to all use cases

AssessmentCross-Industry

A trace from every CMDB data source to its identification rule

Integration Team

A typical ServiceNow assessment for a team whose imports create duplicate configuration items: each data source traced through import set or IntegrationHub ETL to the Identification and Reconciliation Engine, with the fix for each.

ServiceNow consulting

Overview

This is a typical engagement for a team whose CMDB is fed by several import sets, a Service Graph Connector and a custom script. Duplicate configuration items appear after imports and nobody can say which source creates them. AceMQ engineers, with a partner subject-matter expert where needed, trace the sources and write the assessment.

Challenge

ServiceNow documents that import sets and standard transform maps do not apply IRE by themselves. For import sets, the CMDBTransformUtil API is called from the onBefore transform map script and ignore is set to true so the record is not inserted twice. Each import set should have one transform map, the API does not validate mandatory fields, and IRE cannot be applied to dependent CIs. IntegrationHub ETL applies IRE automatically: source data lands in staging tables, the Robust Transform Engine maps it, and IRE reconciles it before the write.

Environment

A ServiceNow CMDB fed by scheduled import sets with transform map scripts, a Service Graph Connector, an ETL definition built in IntegrationHub ETL and a REST integration that writes CIs.

Approach

AceMQ engineers list every source that writes CIs and trace it through its path. They read the transform scripts for the CMDBTransformUtil call and ignore handling, review the ETL definitions and identification rules, and use the CMDB Integrations Dashboard to see runs, results and errors. Each source gets a verdict and a fix.

Solution

  1. Inventory of CMDB data sources with their path: import set, IntegrationHub ETL or Service Graph Connector
  2. Script review for the CMDBTransformUtil call, ignore handling and class mapping
  3. Identification rule review, including dependent CIs where IRE cannot be applied
  4. ETL review: one map per data source, nested payloads, sample test and run schedule
  5. Dashboard findings from the CMDB Integrations Dashboard
  6. Fix list per source, in order of duplicate volume, with a rehearsal plan in a sub-production instance

Outcome

The engagement delivers a written assessment with the path and verdict for every source, the fix list, the rule changes and a rehearsal plan. The customer's team applies the fixes, or AceMQ can apply them alongside them.

Technologies

ServiceNowCMDBIntegrationHub

Ready for a ServiceNow Health Check?

AceMQ's senior ServiceNow engineers have handled this exact type of engagement before. Whether you need architectural guidance, hands-on remediation, or an ongoing managed partnership, we're ready to help.