Disable Staleness for Vmware Instances

[Nathan Okh]

We do not want to include VMWare Instances in cmdb_ci_vmware_instance to effect our Staleness record. However, every time I try to modify it in CMDB CI Class Manager it gives this warning and does not change the health score.

"

Discovery marks VMware vCenter CIs that no longer exist as stale, which takes precedence over the CMDB Health staleness rule defined for the CI. These CIs health results source is set by the instance to Cloud Discovery.

"

Any help would be great

[Rahul Priyadars · Accepted solution]

try doing this..

 Staleness Metric for that particular class from the default 60 days to multiple years (3, 5 or 7).

also see if this property helps u

glide.cmdb.health.src.cmdb_health_audit_only

When set to true, disables health results from sources other than CMDB Health audit (such as cloud discovery). Only results generated by CMDB Health audit appear in the CMDB dashboard. For example, by default, if a CI is determined to be stale by Discovery, then that CI appears as stale in the CMDB dashboard even though CMDB Health audit did not determine that CI to be stale. To disable these stale CI health results, set the property to true. Type: true | false Default value: false Location: System Property [sys_properties] table.

Regards

RP

[Nathan Okh]

This helped, this led me to find a KB from Servicenow. https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0725777

[SandyBatcheller]

The only way we were able to remove this class from our staleness score was to add a condition in the Health Inclusion Rules - staleness to exclude it at the base cmdb_ci table level

Hope this helps,

Sandy