View CMDB health reports

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 dashboard requires some configuration before it can display meaningful data. Once CMDB Health is configured and the CMDB Health Dashboard Jobs are enabled, the dashboard displays data that is automatically collected and calculated on a recurring schedule. The CMDB dashboard is based on the dashboard framework, and uses its capabilities. The CMDB dashboard is domain aware.

Using the CMDB dashboard requires the asset or itil role, and if the system property glide.cms.enable.responsive_grid_layout exists, then its value must be true. For more information, see Enable responsive dashboards.

Access the CMDB dashboard by navigating to Configuration > CMDB Dashboard > CMDB View. On the CMDB dashboard:
  • Click CMDB Health Dashboard Jobs to enable and manage the jobs that monitor and collect health data for CIs and CI relationships.
  • Click the default CMDB Dashboard - CMDB View dashboard to list additional CMDB drill-in dashboards.

The CMDB dashboard has two viewing modes. Click CI Health or Relationship Health to toggle between them.

CMDB Health view

The CMDB Health view is the default view for the CMDB dashboard. It contains scorecards detailing the overall health of CIs in your CMDB, per health KPI and metric. Also, it contains useful reports showing a breakdown of any duplicate, orphan or stale CIs by class, and lists the top 10 incident, alert, and change generating CIs in the CMDB.

All the default widgets in the CI Class view can be filtered using the CMDB class hierarchy tree. Initially, the class hierarchy filter is set to the root class, Configuration Item (All). Click All to select a different class, filtering all widgets on the dashboard to display data only for the selected class and its child classes.

In each scorecard widget, the horizontal bar in the center and the % number are correlated, displaying the aggregated health summary for the KPI. Health results of associated metrics are displayed underneath, each contributing according to the configuration of the metric scorecard, and its threshold.

Except for the Overall health scorecard, you can drill into any widget in the CI Class view:

  • In a scorecard widget: Click the large aggregated percent number or the health bar to drill into a more detailed dashboard for that KPI.
  • In a charts widget: Click a bar to display a list of all the records that the bar represents.
  • In lists: Click the ‘i’ icon to view a list of all the tasks or alerts related to the CI.

Relationship Health view

The Relationship Health view displays various scorecards for health indicators of CI relationships in your CMDB. It contains charts detailing any duplicate, orphan or stale relationships, broken down by relationship type. You can drill down these charts for further details.

Changing the CI Class selection while in the Relationship view has no effect on the data displayed in this view.

Color codes

Both, the CI class view and the relationship view, use color codes when displaying aggregated health status. The status definitions are based on each scorecard’s threshold limits that are defined in the CI Class Manager.

Color code Definition Default threshold setting
Green Best Less than or equal to 33
Orange At risk More than 33 and less than or equal to 67
Red Critical More than 67
Gray Incomplete N/A
Note: The icon is a notation that the maximum failure threshold for the scorecard has been reached. The tests for the metric are halted for this cycle, and all associated aggregated summaries are 0%. Review the scorecard rules which might be ineffective, or the CMDB might be in an unstable state.

Domain separation

If the Domain Support - Domain Extensions Installer plugin is activated, then the CMDB dashboard is domain aware:
  • The CMDB dashboard aggregates and reports health failures and scores based on user’s domain visibility of CIs. If domain visibility lets a user see a CI, then the audit rule in that user’s domain applies to that CI, whether the CI is in the user's domain or in a contained domain. If a CI fails health tests from different user domains, then separate failure records are created.
  • Users can configure KPI and metric settings specific to the needs in their domain. So different domains can have different settings such as active/inactive, and thresholds.
  • A child domain derives its immediate parent's domain health configurations if the child domain does not configure its own. A child domain can override parent's configurations by modifying them.