CMDB Health

The CMDB Health dashboard tells you whether your configuration data can be trusted. Four measures sit at the top, and each one maps to a specific next action.

The four measures

The top of the dashboard carries four data-quality measures. Each has a section below it with the supporting detail.

Duplicate candidates

Pairs of configuration items the platform suspects are the same asset, grouped by match rule and by review status. Work the queue to merge or dismiss each pair. Unresolved duplicates distort every count downstream, so this is the first measure to clear. If this tile reads Detection not configured, the capability is off rather than the data being clean; see below.

Check-in freshness

How recently configuration items were confirmed by a source, whether discovery, an integration, or a person. A number that does not move over time usually means sources are not reporting, not that your data is stable. Once an integration is feeding the CMDB, watch for stalls rather than absolute values.

Field population

Average completeness across the tracked fields. Raise it structurally rather than by hand: make fields required by status, enrich in bulk, and fix the import mappings that leave fields blank. Aim above 80 percent on the fields you govern.

Relationship coverage

How many configuration items carry the links you expect, to a user, a service instance, or a contract. Prioritize linking hardware to its users and every configuration item to its one service instance, since incident routing and affected-SLA logic depend on those links.

Lifecycle and financial

Below the four health measures, the Lifecycle & financial section holds configuration item status, warranty, age, and total value. Read these as descriptions of your estate rather than health alarms. They tell you what you have, not whether the data is trustworthy.

Two empty states

Tiles distinguish two kinds of empty, and the difference matters:

• No data available: the measure is working and there is nothing to show yet.
• Detection not configured: the underlying capability is not turned on. For the duplicate tiles, this means reconciliation is not running.

If a tile reads Detection not configured, the next action is to turn reconciliation on and connect a source. See Getting Started with Reconciliation.