CMDB Staleness

[Community Alums]

Hi All ,

We are using OOB staleness rule and as per that CI would be marked as stale if it is not updated from last 60 days .

but I can see some of the  CI which are not updated from less than 30 days are also marked as stale .

Any suggestion how I to unearth the cause.

[Hitoshi Ozawa · Accepted solution]

Cloud including vCenter staleness is evaluated when discovery is executed instead of waiting days as when discovering internal devices. That is, if the ci can't be found, it's marked as stale because cloud resources should always be available.

https://docs.servicenow.com/bundle/orlando-it-operations-management/page/product/discovery/concept/c...

[Patrick DeCarl1]

I suggest checking out post/link below for how to setup CMDB health dashboard and how you can filter what CIs are review. 

 https://community.servicenow.com/community?id=community_blog&sys_id=cf19ef28dbf59890190dfb24399619c2

[Steele Smith]

Rajat,

You can look in the table cmdb_health_staleness_rule to see the full list of CI classes that have stale rules applied to them and the duration.  This is the quick way to locate a particular rule that may be setup incorrectly.  You can just delete it from there.

The recommended method (I believe) is to use the CI Class Manager > Health > Correctness > Staleness Rule to setup and modify as required.

 As Hozawa mentions above, with Virtual Machines they will be marked stale immediately when they are no longer active in vCenter.  For this type of issue you may want to consider creating a Stale Remediation Workflow to set do another quick discovery of the CI to verify.  My organization chooses to set them the Operational Status to Non-Operational and Status Retired.  Then we just close the Stale Task.

Here's an example of one:

Richard has a great post here about Remediation: https://community.servicenow.com/community?id=community_blog&sys_id=f7fca6a5dbd0dbc01dcaf3231f9619fa

There's a really good tutorial on setting up this workflow but for the life of me I can't find it at the moment.  I think it was either K20 or K19 content.

[Ashutosh Munot1]

Agree. BUt this issue if something else. because for VCenter the stale rule works differently when discovery runs.

Thanks,
Ashutosh