Update Staleness Rule for Database CIs Based on Server Install Status

[ayush_g]

I want to update the staleness rule so that database CIs are marked as stale only when their associated server is in an Installed status

Database CIs are evaluated for staleness only if the related server is in Installed status.

Please share how to implement this ask step by step 

[Tanushree Maiti]

Hi @ayush_g 

 Staleness rules are used to determine the percentage of stale CIs in the CMDB. This sum is then aggregated into the correctness KPI, and weighs into the overall CMDB health calculation. 

To mark database Configuration Items (CIs) as stale in ServiceNow, create a CMDB Health Staleness Rule defining an "Effective Duration" (e.g., 60–90 days) for specific classes.

 These rules evaluate the sys_updated_on field // if a CI is not updated within this timeframe, it is flagged on the CMDB Health Dashboard. 

Note: "Database CIs are evaluated for staleness only if the related server is in Installed status."

 Your requested condition is not aligned with the staleness feature/scope provided by ServiceNow.

Refer this :

Create or edit a CMDB Health staleness rule 

[ayush_g]

Hi @Tanushree Maiti ,

Thanks for response but can you please help me in as requestor is stucked and not ready to accept  for this if it could not  be implemented and asking for apply business rule , flow or other method 

What should we do then 

Thanks