A CMDB Administrator wants to use the Staleness metric from the CMDB Health Dashboard Correctness...

The default staleness threshold is 60 days . A CI is considered stale when it has not been updated within the applicable staleness interval. The update may normally come from Discovery, Agent Client Collector, Service Graph Connectors, IntegrationHub ETL, or another governed source.

Staleness is important because an old CI record may no longer represent the actual environment. Stale data can distort service-impact analysis, misdirect incidents, undermine change-risk calculations, and generate inaccurate operational reports. The guide identifies stale CIs as a core CMDB data-quality condition monitored through CMDB Health.

The 60-day value is the default, not an immutable platform rule. Administrators can configure appropriate thresholds by CI class and organizational requirements. Frequently changing cloud resources may require a shorter period, while stable infrastructure may justify a different governed interval.