У нас вы можете посмотреть бесплатно CIS-DF--Day15 - Discovery Phase Discovery Admin Workspace или скачать в максимальном доступном качестве, видео которое было загружено на ютуб. Для загрузки выберите вариант из формы ниже:
Если кнопки скачивания не
загрузились
НАЖМИТЕ ЗДЕСЬ или обновите страницу
Если возникают проблемы со скачиванием видео, пожалуйста напишите в поддержку по адресу внизу
страницы.
Спасибо за использование сервиса ClipSaver.ru
Day 15 focused on understanding how ServiceNow Discovery works behind the scenes, the technical components involved, and how Discovery supports CMDB population. 🔍 What Discovery Does ServiceNow Discovery helps identify all IT infrastructure components (servers, network devices, cloud resources, printers, databases, etc.) by scanning your environment and updating the CMDB. It works on: Windows / Linux / MacOS AWS / Azure / GCP cloud environments Network devices Virtualization platforms 🌐 Core Workflow: The 4 Phases of Discovery 1️⃣ Scan Discovery “knocks on the door” of an IP. If connection fails → Connectivity issue. 2️⃣ Classify Identifies device type: Server? Router? Printer? If classification fails → Permission issue. 3️⃣ Identify Checks if the CI already exists using unique identifiers: Serial number MAC address Hostname IP address Decides whether to Create or Update a CI. 4️⃣ Explore Collects detailed attributes (more data). Driven by Patterns, Probes, and Sensors. 🧠 Key Components Behind Discovery ECC Queue Acts as the communication channel. Sends outbound probes and receives inbound results. MID Server Runs inside customer network. Executes probes, sensors, patterns. Sends results back to ServiceNow. Probes Small scripts that discover data on remote devices. Sensors Process probe results and update CMDB. Patterns Step-by-step logic for deeper exploration. If pattern not found → No data returned. 📘 Discovery Schedules & Ranges You can create: Multiple schedules for different IP ranges Separate schedules for different cloud providers (AWS, Azure, GCP) 🅰️ Guided Setup & Maturity Model ServiceNow recommends a Crawl → Walk → Run → Fly approach: Crawl Understand basics Install MID Server Create credentials Validate connectivity Walk Use Discovery Workspace Start scheduling discoveries Run Introduce cloud discovery Manage anomalies, diagnostics Fly Integrate patterns, multi‑cloud setups, advanced tuning 🔗 Discovery vs Service Mapping Discovery = Horizontal discovery (components only) Service Mapping = Top‑down mapping (application services & dependencies) Both are separate licensed modules Discovery feeds data into Service Mapping