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

[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

[its_SumitNow · Accepted solution]

@AHMED OLAGUNJU 

Or in other terms 

A CI becomes stale because time has passed beyond the configured threshold without any update. A missing Data Refresh Rule is the cause of why nothing is updating it , not the direct classification condition itself.

Hope you got your solution, if yes then please mark Helpful & Accept the Solution 

Regards

Sumit

[its_SumitNow]

@AHMED OLAGUNJU  Hope You got to review my response, if it helped ,kindly mark helpful & accept the solution so that this thread gets closed 🙂

Regards

Sumit

[yashkamde]

Hello @AHMED OLAGUNJU ,

The classification doesn't depend solely on Data Refresh Rules. Instead, it's based on last update activity. If an Ootb CI hasn't been touched by discovery, integration, or manual updates within the staleness threshold, the CMDB Health Dashboard flags it as stale.

If my response helped mark as helpful and accept the solution.