Overview
Effect on stopping Discovery on certain CI classes.
IMPACT
If Discovery on certain CI classes are stopped then it can affect the following:
- Relationships to the original CI (If discovery has already been conducted once and then if discovery is stopped then the child/parent CI will show empty)
- Child classes information that is discovered by triggering Multiprobes
Example
Consider the example where we are discovering Windows Computers. First we trigger Windows classification probe. This probe after classifying the CI as Windows Computers triggers multi-probes such as "MultiProbe-Windows - ADM", "WMIRunner-Windows - OS Information", "WMIRunner-Windows - Installed Software" and many more as show in the screenshot. These multi-probes fetches additional information regarding the applications running on this Computer CI, OS-Information and Softwares installed on this computer.
If we stop discovery on Windows Computer class CI itself, then it will not discovery the applications running on this Computer CI, OS-Information and Softwares installed on this computer. This way we will not fetch any information regarding Windows - Active Processes and Windows - Active Connections thereby affecting the child classes too. Further if the discovery for computer CI is stopped it will not discover all the neighboring devices connected to this computer. This will affect cmdb_rel_ci table which populates the relationships between CIs.