We are implementing Discovery for the first time and were quite surprised (and impressed, and overwhelmed) by the amount of information that Discovery was able to pull in.
For example: Running a quick discovery on 1 windows server alone created 68 CIs in 15 different classes.
Breaking down the problem:
- How do you identify the CIs that were created via that particular scan? The discovery status shows only the main device. Filtering the cmdb_ci list by created date is not helpful if you are discovering more than one device at a time on a given day:
The ability to identify the CIs created via a particular scan is also important in the case we want to delete all the CIs related to this scan to attempt a fresh scan - since we are just starting out with Discovery and performing a lot of different tests. - Once you can identify a list of CIs that were created via a particular scan/a list of CIs associated to that particular device, how do you get a list of all the field values that were populated via Discovery for each CI?
Is there a more efficient way than going to each CI type, viewing or exporting a list of CIs created for that class including the fields specific to that class?
If 15 different CI classes were created, that's 15 different lists to manually check -- and that's just for 1 windows server scan alone. This number increases significantly the more types of devices are scanned. How have other organizations tackled this challenge?
