why do i see stale ci's while there's no active staleness rule

[Ronald van den]

I'm working on the cmdb health dashboard and to start with we don't want to use the staleness rules.

I only found one ootb rule on the top ci class which i deleted. Then i ran correctness score calculation, cleared browser cache.

But i still see non compliant stale ci's on the dashboard.

Any ideas how i can resolve this?

[AndyB5000]

Did you remove the OOB staleness rule?  OOB the rule is set to 60 days.  If you did remove the rule and you are still showing the stale CI's it is because the CMDB health script ran at some point and identified the stale assets and update the report.  They have been flagged as stale and will continue to show until they are updated.  We came across this also in the audit part as we had audit rules running at one point but have since turned them off and the audit failures still appear on the dashboard.

Hope this helps..

Andy

[Ronald van den]

Thanks for thinking with me...

>>Did you remove the OOB staleness rule?

Yep

Meanwhile i tried updating those old ci's...didn't help.

Re-added a staleness rule scoping all ci's with a day period of 2000, way longer than the oldest ci in our database, didn't help.

I also noticed i can delete the staleness audit record per ci and that seems to work, i don't know if it's the correct way of working, specially since there a few hundred ci's with the same issue.

Strange thing also is that in that audit record it shows a Last Evaluated On, which shows a date of 2 years back.