Contents

CMDB Health

SAVE AS PDF

CMDB Health

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.

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

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.

This is an overview of domain separation as it pertains to CMDB Health. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can then control several aspects of this separation, including which users can see and access data.

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

The CMDB dashboard serves as a central location to view aggregated health reports for your CMDB at a glance which helps you understand the CMDB health status. Also, it provides functions to address health issues, and improve CMDB health.

The CMDB service dashboard serves as a central location to view aggregated health reports for services at a glance. Also, it lets you drill into a service to perform remediation actions that address health issues, and that improve CMDB health. The CMDB service dashboard uses the Performance Analytics framework for dashboards and employs the capabilities it provides.

The CMDB group view dashboard serves as a central location to view aggregated health reports for CMDB groups at a glance. Also, it lets you drill into a CMDB group to perform remediation actions that address health issues, and that improve CMDB health. The CMDB group view dashboard uses the Performance Analytics framework for dashboards and employs the capabilities it provides.

The CI dashboard is a central location displaying health report for an individual CI, history of changes to the CI in a timeline view, and the relation formatter. The CI dashboard also displays incidents, changes, and other tasks affecting the CI, and business services affected by the CI. You can access the CI dashboard from a CI form, or from the CMDB dashboard.

View aggregated orphan, stale, and duplicate CI relationships in the CMDB dashboard. You can configure the relationship scorecards, but you cannot configure the underlying relationship KPI health tests.

A CMDB remediation rule is associated with a task that was created for a failed CMDB health test. A CMDB remediation rule is applied automatically or manually to execute a remediation workflow that can, for example, delete stale CIs.