How to troubleshoot CMDB Health inclusion rulesSummary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Troubleshoot issues with CMDB Health inclusion rules that define which configuration items (CIs) are evaluated for health metrics (completeness, correctness, and compliance) and displayed on the CMDB Health Dashboard. Misconfigured inclusion rules can cause: Metrics not running for expected CI classesDashboard showing empty or incorrect scoresPerformance issues due to overly broad scope About inclusion rules Inclusion rules filter CIs for health calculations and dashboard display. They apply to metrics including Required, Recommended, Duplicate, Orphan, and Staleness. Inclusion rules are stored in the CMDB Health Config [cmdb_health_config] table. To configure inclusion rules: Go to CI Class Manager > Health > Common symptoms SymptomPossible causeDashboard shows no data for key classesInclusion rules exclude critical CI classes such as servers or virtual machinesMetrics applied to wrong classesMetrics configured for unnecessary classesPerformance degradationInclusion rules too broad (for example, all [cmdb_ci] records included)Jobs stuck or timeoutOverly large scope causes Daily Time Out Pause or Max Failures status Troubleshooting steps Step 1: Verify inclusion rules Go to CI Class Manager > Health > Health Inclusion Rules.Verify the following: Classes are included (for example, cmdb_ci_server, cmdb_ci_vm_instance).Conditions are applied (for example, Operational status = Operational, retired CIs excluded). Confirm rules exist in the CMDB Health Config [cmdb_health_config] table. Step 2: Validate metric scope Inclusion rules apply per metric: Completeness metrics: Required and Recommended fieldsCorrectness metrics: Duplicate, Orphan, and Staleness Step 3: Check job status Go to CMDB Health Dashboard Jobs.Verify job status in the CMDB Health Metric Status [cmdb_health_metric_status] table. Possible states: Complete, Max Failures, Daily Time Out Pause To review processing depth by class, check the CMDB Health Processor Status [cmdb_health_processor_status] table. Step 4: Reduce scope if needed If jobs fail or timeout: Narrow inclusion rules to principal CI classes such as servers, virtual machines, and network gear.Apply lifecycle filters: Filter by Install status or Operational status.Exclude retired or decommissioned CIs. Note: Avoid including all classes, as this impacts performance. Step 5: Rerun jobs After changing rules, rerun CMDB Health jobs.Validate dashboard data after job completion. Tables involved TableDescriptionCMDB Health Config [cmdb_health_config]Stores inclusion rulesCMDB Health Metric [cmdb_health_metric]Metric definitionsCMDB Health Metric Status [cmdb_health_metric_status]Job run statusCMDB Health Result [cmdb_health_result]Health evaluation results General guidelines for inclusion rules Include only principal CI classes ServersVirtual machinesNetwork gearApplications Apply lifecycle filters Set Operational status to Operational.Exclude retired or decommissioned CIs. Review inclusion rules periodically to avoid scope creep Performance and failure thresholds If Max Failures status occurs: Check the Failure Threshold setting in Health Preferences, stored in the CMDB Health Metric Pref [cmdb_health_metric_pref] table.The default threshold is 50,000 failures. This value can be increased if necessary. Note: Avoid raising the threshold excessively. Instead, refine inclusion rules to reduce systemic failures. Validation checklist After troubleshooting, verify: Inclusion rules include the correct classes and conditionsJobs are active and have run successfullyMetric status shows CompleteDashboard reflects expected CI classes Related Links<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Create health inclusion rule