Options on deleting CI's en masse...

[Josh Smith]

Hello!  We have ran Discovery successfully and setup the SolarWinds Service Graph Connector as a secondary data source, thinking that it might get us some information that we either cannot get from Discovery or will be obtained at a much later date through Discovery, but sadly this does not appear to be the case.  Instead, from everything I can gather, all CI's that have been imported are duplicated information of other CI's Discovery has already imported, but in weird formats.  I'm the only person who works in Configuration Management and I simply don't have the time to audit this stuff with a fine toothed comb.  I got some second opinions from some other folks (some from SN staff as well) and it seems like the best approach to just disable the SW-SGC and remove all CI's that were imported from this integration...as it's causing some reconciliation conflicts and I simply cannot find any value in importing from this source.  

Can anybody provide some insight and opinions on how to go about removing these CI's?  Running a background script seems like the most appealing method at this time to me.  

[Sylvain Santerr]

Hello,  you may want to consider using the Table cleaner for this. Set the table and condition carefully, then let the magic operate. 

[Josh Smith]

Thank you for the suggestion!

[David104]

Hi Josh,

You may be able to use CMDB Data Manager to create a rule to delete any CI's from the Solarwinds SG source.

I beleive that you might need to create a 'retire' policy first to retire the Solarwinds CI's and then use a delete policy to remove those retired CI's.

Given that you are the only person looking at config management, it's probably worth looking at using data manager to automate some of the cleanup activities that might be required outside of Solawinds SG connector also.

Regards,

David

[Josh Smith]

Thank you for the suggestion!