CMDB health metrics

The overall CMDB health score consists of three major metrics which are correctness, compliance and completeness, each further consisting of sub-metrics. Each metric is associated with a scorecard that determines the contribution of the metric to the aggregated health at the overall CMDB level, class, and CI level.

You can configure which metrics and sub-metrics are included in the aggregated calculation, and set their weight in the aggregation. In the base system, all of the major metrics and sub-metrics are included in the aggregated health report.

Overall

An aggregation of the major metrics correctness, completeness and compliance, according to their overall scorecard weight settings.

Correctness

An aggregation of the following sub-metrics, according to the correctness scorecard weight settings.

Orphan
Measures the percentage of orphan CIs in the CMDB. A CI can become orphan if it was unintentionally left in the CMDB when it is no longer needed. A CI is determined to be orphan if:
  • The CI matches the criteria in an orphan rule.
  • The CI doesn’t have any relationship in the relationship table.
  • Data is missing for the CI in its respective table, or in one of its parents' table.
Staleness
Measures the percentage of stale CIs in the CMDB. CI staleness is determined using reconciliation and staleness rules for the CI's class if exist, and the glide.cmdb.health.staleness property. A CI is determined to be stale if it was not updated by the data source that was the last to update the CI, within a certain length of time. The length of time is determined either by the Effective Duration field in the staleness rule, or by the CMDB health system property glide.cmdb.health.staleness as follows:
  • If a staleness rule is not defined for the CI's class, then the glide.cmdb.health.staleness is used for testing the CI.
  • If a staleness rule is defined for the CI's class, then it is used for testing:
    • If the CI fails that test, then the CI is determined to be stale.
    • If the CI passes the test, then it is further tested using the glide.cmdb.health.staleness property.

For more information about how CI staleness and data source precedence rules affect each other, see Define or edit data source precedence.

In addition, a relationship in which a stale CI is a parent or a child, is determined to be a stale relationship.

Duplicate
Measures the percentage of duplicate CIs in the CMDB using identification rules. Only independent CIs are evaluated for duplication. In a set of duplicate CIs, the count of duplicate CIs is the total number of CIs in the set, minus one. The detailed graphs for a duplicate set of CIs display all the CIs in the set.

Completeness

An aggregation of the following sub-metrics, according to the completeness scorecard weight settings.

Required
Measures the percentage of CIs in which fields that are defined as mandatory, are not populated. Missing fields are tagged as incomplete noting that for this CI some information is missing. Required fields are equivalent to the fields that are specified as mandatory in the system dictionary.
Recommended
Measures the percentage of CIs in which fields defined as recommended, are not populated. Out-of-box, no recommended fields are specified.

Compliance

Based on an audit of the CMDB.

Audit
Compares actual values of specified fields, against expected values defined in template audits (scripted audits are not supported). For more information see Create an audit. Create a compliance-type audit, for which the results are calculated into the compliance CMDB health metric.

Relationships

Measures the health of CI relationships, consisting of the following sub-metrics which are not-configurable:

Duplicate relationships
Relationships that have identical parent and child CIs, identical relationship type, and an identical port. Duplicate relationships are displayed per relationship type. In a set of duplicate relationships, the duplicate relationship count is the total number of duplicate relationships in the set, minus one. The detailed graphs for a duplicate set of relationships display all the relationships in the set.
Orphan relationships
A relationship that is missing either a parent CI, a child CI, or both.
Stale relationships
A relationship in which the parent CI or the child CI is a stale CI.

A single relationship can fail more than one health test. For example, a duplicate relationship can also be stale.