How to exclude VCenter from creating stale CIs?

[Erick18]

When a vCenter CI, such as a virtual machine, is removed, the ServiceNow instance marks it as "stale" in the CMDB, using either of these procedures:

• When Discovery runs, it creates an audit record in the Components installed with CMDB Health table for the missing CI and marks the CI "stale".

How do I exclude the Stale CI Audit Record from being generated? 

Thanks,

Erick

[emir]

The right thing to do is to implement the vCenter Event Collector that notifies NOW that a VM has been removed.

Your proposed solution is a workaround for a Lifecycle issue.

[Erick18]

If I implement vCenter Event Collector. Won't stale audit records still be created? See the 2nd point from the ServiceNow vCenter Discovery Doc. 

• If the instance is configured to collect vCenter events, the system can also create a "stale" audit record for the CI in the CMDB Health Result [cmdb_health_result] table from the VmRemovedEvent event, without having to run Discovery.

If the stale audit record is always created, what is the best course of action to remediate the audit record? We don't want to delete the VM record from ServiceNow. Is there a way to keep the VM record and not have the stale audit record created on each subsequent discovery?

Thanks,

Erick

[emir]

The whole intent behind the Event collector is exactly this. Let NOW know of an event on vC between the Discovery runs, so Discovery does not mark the CI stale because it no longer can find it. This is very useful for migration, deletion, etc of VMs.

That should eliminate the need for the workaround you are asking for.