The overall CMDB health score consists of three Key\n Performance Indicators (KPIs) which are correctness, compliance, and\n completeness, each further consisting of sub-metrics. Each KPI and metric is\n associated with a scorecard that determines its contribution to the aggregated health at the\n overall CMDB level, class, and CI level.
\n\n
\n
You can configure which KPIs and metrics are included in\n the aggregated calculation, and set their weight in the aggregation. In the base system, all\n KPIs and all metrics are included in the aggregated health report.
\n\n
\n\n
Overall
\n \n An aggregation of all three KPIs\n (correctness, completeness and compliance), according to their overall scorecard weight\n settings.\n
\n\n
Correctness
\n \n
A KPI which is an aggregation of the following metrics, according to the correctness\n scorecard weight settings.
\n\n
- \n \n
- Orphan \n\n
- Measures the percentage of orphan CIs in the CMDB. A CI can become orphan if it was unintentionally left\n in the CMDB when it is no longer needed. A CI is determined to be orphan if:\n
- The CI satisfies the criteria in an orphan rule. This criteria\n checks for specific attributes that a CI must have, and for CIs that have no\n relationships or that don't have specific relationships.
- Data is missing for the CI in its respective table,\n or in one of its parents' table.
\n\n \n \n - Staleness \n\n
Measures the percentage of stale CIs in the CMDB. A CI is stale if it was not updated within the\n Effective Duration time period that is specified in the\n staleness rule that\n applies to the class.
\n\nThe base system includes a default staleness rule for the\n Configuration Item [cmdb_ci] class, which sets the Effective\n Duration time to 60 days. This rule applies to all extended CMDB\n classes, and can be overridden by class specific staleness rules defined by the user.\n To determine CI staleness, a staleness rule for the CI's class is used if it exists,\n otherwise, the default staleness rule is used.
\n\nIn addition, a relationship in which a stale CI is a parent or a\n child, is determined to be a stale relationship.
\n\nNote: Discovery marks VMware vCenter CIs that no longer physically exist, as stale. By\n default, this setting takes precedence over a CMDB Health staleness rule defined for\n the CI. When drilling-down in the CMDB dashboard to Health Results, the\n Source for CIs determined to be stale by Discovery, is\n CLOUD_DISCOVERY. Setting the\n glide.cmdb.health.src.cmdb_health_audit_only system property to\n true, ensures that the CMDB dashboard displays health results generated only by CMDB\n Health. For more information, see CMDB Health system properties and Discovery for VMware\n vCenter.
\n \n\n \n \n - Duplicate \n\n
Measures\n the percentage of duplicate CIs in the CMDB using identification rules. Only\n independent CIs are evaluated for duplication. In a set of duplicate CIs, the count of\n duplicate CIs is the total number of CIs in the set, minus one. The detailed graphs\n for a duplicate set of CIs display all the CIs in the set.
\n\nFor more details, examples, and troubleshooting information about duplicate metric,\n see the CMDB Health - Duplicate Metric - algorithm\n [KB0726425] knowledge base article.
\n \n\n \n
\n\n
\n\n
Completeness
\n \n
A KPI which is an aggregation of the following metrics, according to the completeness\n scorecard weight settings.
\n\n
- \n \n
- Required \n\n
- Measures the percentage of CIs in which fields that are\n defined as mandatory, are not populated.\n \n Missing fields are tagged as incomplete noting that for this CI some information is\n missing. Required fields are equivalent to the fields that are specified as mandatory in the\n system dictionary. \n\n \n \n
- Recommended \n\n
Measures the percentage of CIs in which fields that are\n set as recommended, are\n not populated. Out-of-box, no recommended fields are specified.
\n\nYou can use the Add Identifier Fields\n In Recommended Rules scheduled job to set criterion attributes from active\n identification rules, as recommended fields. You can use the Remove Identifier Fields In Recommended\n Rules scheduled job to unset criterion attributes from active identification\n rules, as recommended fields.
\n \n\n \n
\n\n
\n\n
Compliance
\n \n
Based on the results of actual CMDB audit runs.
\n\n
- \n \n
- Audit \n\n
Audit compares actual values of specified fields, against expected values defined in\n template and scripted audits. Based on the Last run date of\n audits, CMDB Health identifies the set of the most recent\n complete audit run, and uses those audit results. To pass the CMDB Health audit\n test, a CI must be in compliance with all audits for that CI. Create a\n compliance-type audit, for which the results are calculated into the CMDB Health\n compliance KPI.
\n\nWhen running scripted\n audits, the Last run date is not populated. Therefore,\n for the compliance KPI to include the results of a scripted audit, update the script\n in the audit to record the audit run time.
\n \n\n \n
\n\n
\n\n
Relationships
\n \n
Measures the health of CI relationships, consisting of the following metrics which are\n not-configurable:
\n\n
- \n \n
- Duplicate relationships \n\n
- Relationships that have identical parent and child CIs,\n identical relationship type, and an identical port. Duplicate relationships are\n displayed per relationship type. In a set of duplicate relationships, the duplicate\n relationship count is the total number of duplicate relationships in the set, minus one.\n The detailed graphs for a duplicate set of relationships display all the relationships\n in the set. \n\n \n \n
- Orphan relationships \n\n
- A relationship that is missing either a parent CI, a child\n CI, or both. \n\n \n \n
- Stale relationships \n\n
- A relationship in which the parent CI or the child CI is a\n stale CI. \n\n \n
\n\n
A single relationship can fail more than one health test. For example, a duplicate\n relationship can also be stale.
\n\n
Also reports the following relationship-related summaries:
- Relations not compliant with suggested relations
- Relations not compliant with containment rules
- Relations not compliant with hosting rules
\n
\n\n
\n\n
