Monitoring
and maintaining the health of the CMDB is essential to an effective and continuous use of the
product. Health indicators such as duplicate CIs, required CI fields, and audits contribute to
the calculation of health scorecards at the CI, class, and CMDB level.
The health of the CMDB data is monitored and reported for the following KPIs, each further
consisting of sub metrics:
- Completeness: CIs are tested for required and recommended fields that are not
populated.
- Correctness: CIs are tested against pre-defined data integrity rules such as
identification rules (to detect duplicate CIs), orphan CI rules, and stale CI
rules.
- Compliance: The CMDB data is audited for adherence to pre-defined certificates.
- Relationships: The health of CI relationships is tested for indicators such as orphan
and duplicate relationships. And for compliance with suggested relationships, hosting
and containment rules.
After CIs are tested for various health indicators, the results are aggregated at the class
level, and eventually at the overall CMDB level. You can configure how health is calculated
and the weight of each KPI and each metric at every level of the aggregation. For most
health tests, you can configure the health tests themselves.
CMDB Health is domain aware. If the domain separation plugin has been activated, then the
CMDB dashboard displays health based on data, rules, and settings from the logged-on user
domain. If rules and settings are not defined for a child domain, then the parent's settings
are applied, recursively.
CI remediation
CMDB Health provides a framework for configuring CI remediation. Remediation lets
you proactively apply corrective actions to unhealthy CIs in a managed and standardized
fashion.
Setup
You need to configure CMDB Health related system properties, and health KPI and metric
rules, to customize how aggregated data is calculated and other CMDB Health behavior. To
start gathering and aggregating health data, you need to enable the CMDB Health-related jobs
(CMDB Health Dashboard jobs) which are initially disabled. See Setup and configure CMDB Health for details about enabling these jobs and about
configuring other CMDB Health settings.
