CMDB Health

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 3 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of CMDB Health Extend ServiceNow AI Platform capabilities

    Monitoring and maintaining the health of the Configuration Management Database (CMDB) is crucial for effective product use. CMDB Health analyzes health indicators like duplicate Configuration Items (CIs), required field completeness, and audit compliance to generate scorecards at various levels, including CI, class, and overall CMDB. Note that CMDB Health focuses exclusively on CMDB tables and does not support non-CMDB tables.

    Show full answer Show less

    Key Features

    • Health Metrics: The health of the CMDB is assessed through Key Performance Indicators (KPIs) such as completeness, correctness, compliance, and relationships, each with specific sub-metrics.
    • CMDB Workspace: Access CMDB health details through the CMDB Workspace, featuring important action tiles and dashboards for overall health metrics and specific CI details.
    • CI Remediation: A framework for proactively correcting unhealthy CIs in a standardized manner.
    • Domain Separation: Ensures that CMDB Health is aware of domain settings, allowing for tailored health evaluations based on the logged-in user's domain.
    • Health Dashboards: Centralized dashboards provide insights into aggregated health reports for CIs, services, and groups, enabling remediation actions to improve health.

    Key Outcomes

    By implementing CMDB Health, customers can expect enhanced visibility into the health of their CMDB, better management of CIs through remediation capabilities, and improved compliance with data integrity standards. Ultimately, this leads to a more reliable and efficient configuration management process, supporting better decision-making and operational efficiency.

    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.

    Note:
    CMDB Health doesn't support non-CMDB tables.
    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 experience in CMDB Workspace

    You can use the CMDB Workspace landing page and its views to access CMDB health details that are based on CMDB Health activities and aggregations. For example:
    • Use the Important actions tile on the landing page to access cards with CMDB Health-related tasks such as de-duplication tasks.
    • Use the CMDB Health tile to see overall health metrics for CIs and relationships, to navigate to the CMDB Health and CMDB Relationship Health dashboards, and to drill down to more health details for specific CIs.
    • Use tiles throughout the CMDB Workspace to drill down to health overviews of specific CIs.

    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.

    Domain separation

    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.

    Metric tests from the global domain propagate to subdomains. However, subdomains can have their own local metric tests which override the global domain tests. Up until the San Diego release, subdomain local metric tests were applied to the subdomain CIs and also to the global domain CIs (which are visible on subdomains). Global domain CIs that failed metric tests of local subdomains, could have generated large amounts of data due to duplicated data.

    Starting with the Tokyo release, CIs in the global domain are evaluated only against metric tests specified in the global domain. In subdomains, local metric tests are applied only to the CIs in that subdomain and are not applied to the global domain CIs (even though the global domain CIs are visible in the subdomain). Health results for CIs in the global domain appear on subdomains and health results on subdomains reflect this new behavior.

    See Domain separation in CMDB Health for more information.

    Setup

    To start gathering and aggregating health data, you need to enable the CMDB Health-related jobs (CMDB Health Dashboard jobs) which are initially disabled. You also need to configure CMDB Health related system properties and health KPI and metric test rules, to customize how aggregated data is calculated and other CMDB Health behavior.

    For all the details about setting up and configuring CMDB Health, see Set up and configure CMDB Health.