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.

[Ashutosh Munot1]

Hi,

Is there a specific staleness rule on that table for 30 days?

Every table can have its own stale rule.

Thanks,
Ashutosh

[Hitoshi Ozawa]

Note that beside the cmdb health metric, discovery has it's own set of staleness rule so the 30 days staleness may be coming from discovery.

The Discovery setting of certain types of CIs as stale takes precedence over a CMDB Health staleness rule defined for the CI. 

https://docs.servicenow.com/bundle/orlando-servicenow-platform/page/product/configuration-management/task/t_CreateCMDBHealthStaleRule.html

[Community Alums]

Hello Ashutosh ,

There is no seprate rules for 30 Days .we started discovery one month back that why I was referring to 30 days .

Hello Hozawa ,where I can found those discovery rules .

FYI all the stale entry for Vcenter related classes .

[Ashutosh Munot1]

Hi,

If you do to CI Class manager then you can select vCenter class and then see the rules.

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

Check this it explain why this is happening for you vCenter.

Thanks,
Ashutosh