handling stale data from SN Discovery?

Ravish Shetty · ‎05-23-2019

how is stale data handled? do we need to work it through the CMDB health dashboard and configure additional remediation rules or is the CI record automatically marked as non-operational?

We will be performing SCCM data pull, ServiceNow discovery (workstation, network devices, VM) and Azure/VMWare VCenter service account data pull.

doug_schulze · ‎05-23-2019

For base classes, yes you will have to make a determination to how they are remediated in your CMDB. I did a lab a few years back at K16 that built a (very basic) structure for CI Lifecycle, perhaps you can find some inspiration from that?

And while I havent messed with it, the CMDB team also has a level of CI lifecycle that may be of use.

View solution in original post

Amit Sharma4 · ‎05-23-2019

Hi Ravish,

First step will be to keep the discovery and imports updated and troubleshoot the CIs, which are not updated. If there is a trend, try to fix that.

Second will be to keep a closer look on the ci classes and the discovery source. There can be the classes, which you might not be interested to manage like VMware Virtual Machine Instance.

To keep dashboard healthy, you can put some business rule to keep devices in retire state.

Thanks

Amit

Ravish Shetty · ‎05-23-2019

thanks Amit