Thousands of Stale CIs but no Stale CI Remediation Tasks

[Phil32]

We are newly trying to set up our CMDB dashboard and remediation rules.  Starting with the Staleness metric for a single class to test, as we know it will need to delete over 400,000 stale CIs.

The job came back with what looks like a list of Stale CIs, but doesn't generate a STAL task

The really weird part is, the Last Evaluated On date is from the previous week

[Phil32]

Forgot to include a screenshot of the rule

[Phil32]

We just noticed the Correctness Scorecard is showing that Staleness is not evaluated, but Duplicate and Orphan are.  That is really weird because we have only set a single Staleness rule so far.

[richardbrounste]

Go to the CMDB Health Metrics and make sure that the Failure Threshold for Staleness is set to a very high value like 500,000 since you have so many CIs.

Configuration -> Health Preference

Health Metrics on the right hand side and select metric:  "Staleness"

Set the Failure Threshold to: 500000

Then, manually run the Correctness job:

Configuration -> Health Preference

Scheduled Jobs

Click on CMDB Health Dashboard - Correctness Score Calculation and run it.  You don't have to make it Active unless you want the job to run on a scheduled basis.

Go to the cmdb_health_metric_status table to view the status of the job and make sure it runs to completion.

Also, clear the browser cache.  If you are using Jakarta or older, it needs the cache cleared if you are going to view the results right away.

[Phil32]

That got us closer, but still missing something.

1st, our job timed out due to so many stale CIs.  But it did create some STAL tasks.

STAL tasks were generated, but they aren't set for active.

In table view, the CIs listed only have a SYSID.  However, none of those SYSIDs are found on the cmdb_ci_vmware_instance table.