Monitoring CMDB data quality using dashboard metrics in CMDB success advisor for Data Foundations

concept brazil Updated Oct 5, 2026 9 min read cmdb-sa-df-dashboard.md
Raw file servicenow.com

The CMDB success advisor for Data Foundations dashboard enables CMDB administrators to identify and address data quality issues specific to principal classes in the Configuration Management Database (CMDB).

Note: Charts display up to the top 10 values. Any remaining values are grouped into an Others category. When you select a segment or count on a chart from a CMDB success advisor dashboard, the KPI Details page opens. On the page, you can analyze how a specific metric trends over time. Additionally, the Remediation actions panel appears when remediation actions are available for that card. Use the panel to improve the quality of CMDB. To learn more, see and Improving CMDB data quality for Data Foundations.

[Omitted image "cmdb-sa-df-dashboard.png"] Alt text: CMDB success advisor for Data Foundations dashboard overview.

Note: If the Performance Analytics data collector exceeds its row limit during data processing, a notification banner appears on the dashboard indicating that some metrics could not be loaded. For more information, see .

Access the dashboard

To open the dashboard, select View insights for Data Foundations on the CMDB success advisor landing page. See Access CMDB success advisor. The dashboard header displays a Last updated timestamp reflecting the completion time of the most recent Data Foundations data collector job run.

Note: The CMDB success advisor for Data Foundations dashboard is available only after the setup process is complete. For more information, see CMDB success advisor for Data Foundations setup.

Required roles

Role Description
sn_cmdb_admin Required to access the Data Foundations dashboard.
sn_cmdb_user Provides read-only access to CMDB success advisor pages and data, including the AI-generated summary of the dashboard.
sn_cmdb_editor Provides the same dashboard access as sn_cmdb_user, with write access on CMDB records outside the application.

Use cases

For examples of how different people in your organization would use this dashboard, see these use cases.

User

Dashboard use

CMDB administrator

  • Monitor CI attribute completeness across principal classes
  • Identify classes at risk with low data quality scores
  • Detect stale and duplicate CI records affecting CMDB data accuracy
  • Evaluate integration coverage to confirm the right sources populate the CMDB
  • Prioritize remediation efforts based on incident, change, and problem impact
  • Track progress toward CSDM alignment
## Dashboard features

The dashboard provides insights into principal CI class data quality and completeness. Use the dashboard to identify and resolve data quality issues within the CMDB through dedicated sections, filters, indicators, and visual reports. Gain insights into CMDB performance related to Data Foundations. Targeted CMDB metrics focus remediation efforts. Regularly monitor these metrics and follow suggested remediation actions to systematically improve CMDB data quality over time.

Note: The dashboard data is filtered based on the Selected principal classes and Date range filters. See Filters.

Feature

Description

CMDB data quality insights generated by AI

Displays an AI-generated summary of CMDB data quality for Data Foundations outcomes and lists the top 5 issues with guided remediation actions.Issues are ranked primarily by the percentage of CIs or CI classes that each issue affects, not by severity. They fall into four categories, in this order: Data integrity, CI attributes, Reconciliation and governance, and Data Manager policies. Foundational data integrity issues, such as duplicate CIs and stale CIs, are evaluated first because they can inflate the counts behind other issues.

A percentage gap of more than 15 points between issues in the same category can change their default order. A percentage gap of more than 40 points between issues in different categories can also change their default order. For the reasoning behind the ranking and recommendations, see Summarize CMDB readiness with the ServiceNow Otto skill.

Select View reasoning to open the Reasoning popover, which explains the ranking and includes a Learn more link to the same topic.

Note: Available only when the summarize CMDB readiness skill is configured. See Configure the summarize CMDB readiness skill.

CIs by principal class

Displays the breakdown of operational CIs by principal CI class to highlight CI distribution in the CMDB.

CIs by data integration source

Displays the breakdown of operational CIs by data integration source to highlight their contribution to CMDB population.

CIs missing key attributes

Displays completeness metrics per principal CI class, identifying classes below the defined threshold.

CI data quality issues

Displays key metrics related to CIs that have not been updated or may have duplicate records, leading to outdated information and inconsistencies in the CMDB.

## Filters

Filters enable narrowing the data shown in graphs and metrics based on principal class, date range, or stale CI threshold.

Name Type Description
Principal classes List Filters CIs based on the selected principal classes.
CI class categories List Filters data based on CI category. Only available when the CMDB CI Class Models plugin (sn_data_model_nav) is active and you have read access to CI class data.
Date range Date Filters the dashboard data based on the selected date range.
Stale CI List Filters stale CIs based on the number of days since their last update. Available values: 7, 14, 30, 60, and 90 days.

Select Reset filters to clear all filter selections and restore the dashboard to its default view.

Note: The pa_viewer role is required to use the filters, including Reset filters.

CIs missing key attributes

Key metrics for the completeness of CI attributes across principal classes, identifying gaps that affect data quality.

Note: The percentage change comparison on the CIs missing name, CIs missing location, and CIs missing managed by group cards covers the most recent 6 months of data.

When at least 5% of CIs are missing managed by group, the CIs missing managed by group card checks the principal classes of those CIs. If the CMDB setting that syncs managed by group values to CIs is turned off, the card summary notes that the sync setting is off. If one or more of those classes are missing the managed by group field, the card summary names those classes.

Card Description Indicators
CIs missing name Total number of CI records from principal classes missing a name, measured daily, where the CI does not have a name specified. CIs missing name
CIs missing managed by group Total number of CI records from principal classes missing a managed by group, measured daily, where the CI does not have a managed by group assigned. CIs missing managed by group
CIs missing location Total number of CI records from principal classes missing a location, measured daily, where the CI does not have a location assigned. CIs missing location

CI data quality issues

Key metrics for CIs that have not been updated or may have duplicate records, leading to outdated information and inconsistencies in the CMDB.

Note: The KPI Details trend chart for the Stale CIs and Duplicate CIs cards covers the most recent 6 months of data.

Card

Description

Indicators

Stale CIs

Principal class CIs not updated within the expected maintenance window, causing data gaps and inaccuracies that affect incident and change impact analysis. Additionally filtered by the Stale CI filter.When you select a segment on the Stale CIs chart, the KPI Details page title reflects the Stale CI filter value selected at the time. For example, the title can read "CIs not updated in last 30 days".

CIs not updated in last 7 daysCIs not updated in last 14 days

CIs not updated in last 30 days

CIs not updated in last 60 days

CIs not updated in last 90 days

Note: The CIs not updated card data is additionally filtered based on the Stale CI filter. See Filters.

Duplicate CIs

Operational CIs identified as duplicates within principal classes, causing ambiguous CI selection in processes and data redundancy.

Duplicate CIs

The Stale CIs card and the Duplicate CIs card each display their own **Ask Otto** action. This action is separate from the Remediation actions panel. For more information about the Remediation actions panel, see [Improving CMDB data quality for Data Foundations](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/servicenow-platform/configuration-management-database-cmdb/cmdb-sa-df-remediation.md).

Selecting Ask Otto on either card starts an agent conversation immediately, rather than waiting for the next scheduled agent run. The Duplicate CIs card's action is available only when the CMDB Duplicate CIs Agent is active for your instance.

Selecting Ask Otto opens the ServiceNow Otto panel in a dialog box. The panel starts the CMDB Staleness Agent conversation for the Stale CIs card, or the CMDB Duplicate CIs Agent conversation for the Duplicate CIs card.

The Ask Otto action requires the now_assist_panel_user role. The Stale CIs card also requires the sn_cmdb_editor role. The Duplicate CIs card also requires the cmdb_dedup_admin role.

Note: If the agent conversation fails to start, an error notification appears and the Ask Otto action remains available to try again.

For more information about the CMDB Staleness Agent, see Stale CI remediation using the staleness agentic workflow.

The CMDB Duplicate CIs Agent is part of the Feature Preview Program. For more information, see Feature Preview Program.

Keywords Data Foundations advisor dashboardCMDB data quality metricsprincipal class dashboard indicatorsCIs missing key attributesstale and duplicate CI metricsCMDB data quality insights generated by AI
Search documentation
Search document titles and file paths on the brazil branch