CMDB Health
Below metrics are major on CMDB Dashboard:
- Completeness
- Compliance
- Correnctness
Completeness
Completeness is a measurement that aggregates two sub-metrics that determine how well a CMDB is populated.
Required: Required fields are mandatory. This measurement calculates the percentage of CI’s that are not populated. Missing fields are tagged as incomplete indicating that information is missing for a particular CI.
Recommended : The Recommend fields are self-explanatory — they are recommended, but not required. Again, this is a measurement of the percentage of CI’s that are not populated.
Compliance
Compliance enables administrators to certify CMDB data for correctness and fix any discrepancies found in the data. This is accomplished by defining Audit rules.
Correctness
Correctness is derived from the aggregation of three sub-metrics.
Duplicate: Measures the percentage of duplicate CI’s in the CMDB using identification rules. Only independent CI’s are evaluated for duplication. In a set of duplicate CI’s, the count of duplicate CI’s is the total number of CI’s in the set, minus one. The detailed graphs for a duplicate set of CIs display all the CIs in the set.
Orphan: A CI can become an 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’ tables.
Staleness: A CI’s staleness is determined using reconciliation and staleness rules for the CI’s class, if it exists. Otherwise, there is a system staleness property that is used. A CI is determined to be stale if:
- The CI was not updated by the data source that was the last to update the CI, within the time frame defined in the staleness rule for the class for that specific data source.
- The CI wasn’t updated for the time specified by the CMDB health system property glide.cmdb.health.staleness.