Discovery &
Service Mapping
How does data get into the CMDB automatically? Discovery scans IP ranges and applications, MID Servers bridge network boundaries, Discovery Patterns determine what to collect, Service Mapping builds application dependency maps, and Agent/ACC extends coverage to isolated devices. This part covers the INGEST domain's automated CI population tools.
Key traps: MID Server is required for Discovery on private networks (not public cloud APIs), IP Range Discovery finds new CIs while CI Group Discovery refreshes known CIs, Discovery Patterns populate CI attributes using Probes and Sensors, and Service Mapping builds the CSDM Application Service model. Know when each tool is appropriate and what its limitations are.
Part 3 Study Modules
Discovery Architecture & How It Works
How Discovery populates the CMDB — IP range scanning, Probes (data collectors) and Sensors (data processors), the CI write pipeline, discovery_source field, and Discovery scheduling.
MID Server — The Discovery Bridge
MID Server architecture, when it is required vs. optional, MID Server clusters, capability matching, MID Server Selection policies, and how MID Servers handle credential management for private networks.
Discovery Patterns, Probes & Credentials
Pattern Designer, Horizontal Discovery vs. Vertical Discovery, credential types (SSH, WMI, SNMP), credential alias, Discovery Patterns for Linux/Windows/Network, and how Patterns determine CI class assignment.
Service Mapping — Building Application Dependency Maps
Top-down vs. Tag-based Service Mapping, entry points, Application Service creation, how Service Mapping builds the CSDM Application Service model, Traffic-based Discovery, and service map completeness.
Agent Client Collector (ACC) — Agentless to Agent-Based
When agentless Discovery fails — isolated devices, no network reach, high-security environments. ACC architecture, agent deployment, CI Group-based Discovery for ongoing refresh, and choosing Discovery method by scenario.