Stale CI in CMDB

[AHMED OLAGUNJU]

I am curious about the reason why an OOTB CI will become a Stale CI in the CMDB Dashboard when the CI doesn't have a Data refresh rule.
I want to understand the logic behind the condition to classify an OOTB CI stale in the platform.

[its_SumitNow · Accepted solution]

Hi @AHMED OLAGUNJU 

see Data Refresh Rules are created for updating attributes of a CI right, If Any refresh rule is not present then it is expected to be stale 

As per this property value glide.cmdb.health.staleness , staleness would be measured

Hope my response Helps 🙂

Regards

Sumit

[Abhishek_W]

Hello @AHMED OLAGUNJU 

Out of the box in ServiceNow, a CI can still become stale even if you did not personally create a Data Refresh Rule because the platform already provides default Data Refresh Rules for many core CI classes such as server, network , and computer. Even when you do not see a rule directly configured for a specific class, there may be a global class-level rule applied higher in the class hierarchy, or the CI may inherit a rule from its parent class such as cmdb_ci, or an OOTB rule may have been installed automatically as part of the CMDB Health configuration. Because of this built-in and inherited logic, the CI is still evaluated against an applicable Data Refresh Rule, and if its (sys_updated_on) date exceeds the defined threshold, it will be classified as stale in the CMDB Health Dashboard.   

👍If you find this solution helpful, give a thumbs up, accept the solution✔️