CMDB health audit failure: data quality rules violated

Orphaned configuration items exist where parent CIs have been deleted but child CIs still reference them through relationship records. (high likelihood)

Required attributes defined in CMDB data quality rules are missing values on configuration items, violating mandatory field requirements. (high likelihood)

Duplicate configuration items have been identified that should be merged but remain as separate records in the CMDB. (medium likelihood)

Discovery processes have created CIs with incomplete or invalid data that fails validation against configured quality rules. (medium likelihood)

Custom data quality rules have been configured with overly restrictive criteria that legitimate CIs cannot meet. (low likelihood)

Step 1: Navigate to Configuration > CMDB Health > Health Dashboard to view the detailed health audit results and identify which specific data quality rules are being violated.

Step 2: Check Configuration > CMDB Health > Data Quality Rules to review the configured rules and understand the validation criteria that are failing.

Step 3: Use the CMDB Health Dashboard drill-down features to examine specific CIs that are violating rules and document the patterns of violations.

Step 4: For orphaned CIs, navigate to Configuration > Relationships to identify and clean up invalid relationship records pointing to deleted parent CIs.

Step 5: Address missing required attributes by either populating the mandatory fields on affected CIs or adjusting the data quality rules if the requirements are inappropriate.

Step 6: Use Configuration > Identification and Reconciliation > Duplicate CIs to identify and merge duplicate configuration items that should be consolidated.

Step 7: Review and update Discovery patterns or transform maps if the violations are caused by incomplete data from automated discovery processes.

Step 8: Re-run the CMDB health audit from Configuration > CMDB Health > Run Health Audit to verify that the violations have been resolved.