How to handle stale application CIs?

[VijayataM]

Hi There,

What is the right way to process stale (not updated last 60 days) application CIs?

[Nikhil Bajaj9]

Hi @VijayataM ,

To process stale application CIs (last updated > 60 days), first investigate why  they are stale, as this indicates a potential issue with discovery, integration, or manual processes. Then, use CMDB Health remediation tools to automatically or manually retire, archive, or delete these CIs, setting their status to "Retired" or "Non-Operational" instead of immediate deletion. Regularly audit stale CIs, and if a discovery or integration issue is found, fix it before performing remediation to prevent future staleness. 

[Cindy Trieu]

Hi Vijayata,

I like the answer from this other community post (steps 1&4) which is similar to your situation: https://www.servicenow.com/community/cmdb-forum/what-is-best-practice-for-stale-ci-relationships/m-p... 

This other question is going one step further and asking about the relationships, but steps 1 and 4 here address just the stale CI's.

The definition of stale is that these CI's have not been re-discovered by either discovery or an integration in 60+ days. From here, you will have to determine whether or not they are stale because they are no longer in your system or there is something preventing them from being rediscovered. From there, you will choose the appropriate course of action. The actions can be different for each CI and/or class, so you will have to determine that based on your CMDB.

[Nikhil Bajaj9]

Hi @VijayataM ,