CMDB Health KPIs — What they mean, how scores are calculated, and why CI appear (or don't) on the cmdb health dashboardSummary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Teams are often unsure how CMDB Health calculates Correctness, Completeness, Compliance, and Relationships KPIs, what each metric means, and why certain CIs show up (or dont) on the CMDB Health dashboard. 1) What CMDB Health measures (high level) CMDB Health computes three main KPIs—Correctness, Completeness, Compliance—each made from specific metrics; it also reports Relationship Health with its own metrics. 2) Correctness KPI — Orphan: What it means: % of CIs that look “orphaned” (no expected relationships or missing data/parent-table data).Example: A server CI with none of its required upstream/downstream relationships gets counted as orphan. Staleness: What it means: % of CIs not updated within the Effective Duration of the staleness rule (base default is 60 days, can be overridden per class).Example: A network device untouched for >60 days is stale and lowers the score. (Note: vCenter discoveries can mark items stale and that can supersede a generic rule unless you configure the CMDB Health property to count only CMDB Health audit results.) Duplicate: What it means: % of duplicate independent CIs identified by identification rules (a duplicate set size N contributes N-1 duplicates).Example: Three identical computer CIs (same identifiers) = 2 duplicates for scoring. 3) Completeness KPI — metrics & examples Required: What it means: % of CIs missing fields that are mandatory in the dictionary.Example: A server missing “Serial number” if that field is mandatory will be incomplete. Recommended: What it means: % of CIs missing fields marked recommended (none OOB; can be populated from identifier fields via scheduled jobs).Example: If “Location” is recommended for Routers, a router without Location counts against this metric. 4) Compliance KPI — what it uses & example Audit: What it means: Uses results of CMDB audits (template/scripted) to see if actual CI values match expected values. The KPI picks the most recent complete audit run; scripted audits must record their Last run time to be counted.Example: If a template audit enforces “OS must be Windows Server 2019” and a CI is 2016, that CI fails compliance. (Compliance must be activated to show results.) 5) Relationship Health — what’s checked & examples Reported separately from the three KPIs: - Duplicate relationships: Same parent, child, type, and port counted as duplicates (N-1 logic). - Orphan relationships: Parent or child CI missing. - Stale relationships: Either end CI is stale. Also highlights relations not compliant with suggested/containment/hosting rules. 6) Why something appears (or not) on the dashboard — Health Inclusion Rules Health Inclusion Rules control which CIs are included in calculations and shown on the dashboard for these metrics (required, orphan, recommended, duplicate, staleness). You can scope them by class and domain; child classes inherit parent rules unless they define their own. Examples & caveats: - A rule on cmdb_ci can effectively filter all classes. - Identification inclusion rules also affect duplicate CI visibility because the dashboard uses the Identification Engine. Create health inclusion rule Practical effect: If a team says “we fixed X but the score didn’t change,” check whether inclusion rules exclude that class/CI from evaluation. Conversely, big drops may be because a previously excluded class was included again. 7) Quick "decode" guide you can share with teams Correctness – Orphan: "Do my CIs have the expected relationships and basic data?" Correctness – Staleness: "Have my CIs been updated recently (per rule)?” (Default 60 days unless overridden.) Correctness – Duplicate: "Are there multiple CIs that identify as the same item?" (Based on identification rules; independent CIs only.) Completeness – Required: "Are mandatory fields filled?”" Completeness – Recommended: "Are recommended fields filled?" (You decide what’s recommended.) Compliance – Audit: "Do CIs match policy templates/script rules from the last completed audit run?" (Audit must be enabled.) Relationships: "Are relations duplicate, orphan, or stale; and do they follow suggested/containment/hosting guidance?" Inclusion Rules: "Which CIs are even counted in the above metrics?" (Filter by class/metric; mind global-only for Duplicate.) Related Links<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } CMDB Health KPIs and metrics View CMDB Health Dashboard Configuring CMDB Health Create health inclusion rule CMDB Health system properties Enable and configure a CMDB Health Dashboard job