Video summary

Master ServiceNow ITOM, Discovery & CMDB || Real-Time Projects & Use Cases

Main summary

Key takeaways

Educational

Main ideas / purpose of the video

  • The speaker, Amit, introduces a proposed ServiceNow ITOM (IT Operations Management) training/program.
  • The program combines:
    • Theory
    • Extensive labs
    • A culminating end-to-end “ITOM pipeline” project
  • Amit positions the training as aligned with current and future market demand, explicitly tied to AI/agent-based trends rather than outdated course outlines.
  • He emphasizes that each module starts from architecture/fundamentals and then advances toward implementation and troubleshooting through practice.

Training structure (methodology & learning approach)

Learning format per session

  • ~60% hands-on (answered/labs)
  • ~40% conceptual discussions

Pedagogy / learning approach

  • Start with fundamentals and architecture
  • Move into implementation
  • Use multiple lab scenarios to build troubleshooting ability
  • Include real project experience and explain how solutions apply to customer discovery needs

Customization

  • Amit states he will customize the course per batch demand, including any missed topics requested in advance.

Detailed syllabus (modules, concepts, labs, and deliverables)

1) Module 1 — CMDB (Configuration Management Database)

Main goal: Understand CMDB architecture, scope, and core concepts deeply.

Topics/concepts

  • Class model
  • Relationship
  • Source and data governance
  • Health dashboard
  • Certification and audit life cycle management

Time investment: About 10–15 hours of content (as stated)

Depth approach: Architecture + fundamentals first, then deeper dives.

2) Module 2 — Discovery (Real-time labs + infrastructure discovery)

Main goal: Learn how to use ServiceNow Discovery for real infrastructure challenges, including scanning/management patterns.

Labs

  • At least 5–6 real-time labs

Topics/concepts

  • Architectures fundamentals
  • MID Server architecture
  • ECC (as referenced)
  • Queues
  • Discovery types
  • Discovery patterns
  • Network firewalls
  • Port scanning
  • Troubleshooting approaches (based on problems and solutions)
  • Credentials setup
  • Running discovery
  • Advanced scanning/pattern design (especially for large environments, e.g., “1200 servers”)

Time investment: Around 10 hours (minimum stated)

3) Module 3 — Advanced Discovery

Main goal: Go beyond basic discovery configuration into tuning and custom discovery behavior.

Topics/concepts

  • Discovery schedule
  • IP ranges
  • Patterns deep dive
  • Classification/identification
  • Custom pattern creation
  • Cloud discovery

Cloud focus

  • Covers AWS and Azure (labs for both)

Labs

  • 4–5 labs during the class

Core emphasis: Configure IP ranges and custom patterns, then tune discovery performance/results.

4) Module 4 — Service Mapping

Main goal: Build service maps and understand how traffic/entry points tie discovery to business services.

Topics/concepts

  • Concepts behind service mapping
  • Entry points
  • Service map concept
  • Entry point mapping
  • Traffic-based discovery
  • Service map use and navigations (as referenced)
  • Business service and SLA mapping
  • Service mapping debugging

Deliverables described

  • Mapping business apps and traffic to support downstream incident/service workflows

5) Module 5 — Event Management

Main goal: Detect, correlate, normalize events and drive automated actions (including incident creation).

Labs

  • Includes event instance generation
  • Event rule creation
  • Normalization, correlation, etc.

Topics/concepts

  • Event management architectures
  • Event sources
  • Event tools
  • Alert correlations
  • Maintenance windows
  • Noise reduction
  • AI Ops (explicitly included)
  • Incident auto-creation

Examples of event management lab activities

  • Noise detection
  • Event rule creation
  • Normalize events
  • Alert correlations
  • Auto-create incidents

6) Module 6 — Cloud Management

Main goal: Manage cloud discovery/provisioning/governance/cost with ServiceNow.

Topics/concepts

  • Cloud discovery
  • Cloud provisioning
  • Governance
  • Cost management
  • Cloud CI models

Cloud coverage

  • Both Azure and AWS are included

Labs (as described)

  • Set up cloud + cloud discovery
  • Resource mapping
  • Cost visibility

7) Final / Module 7 — Integrations & “Real Scenario Project” (end-to-end ITOM pipeline)

Main goal: Combine modules into a complete end-to-end pipeline supporting operations and automated workflows.

Core integration/workflow described

  • Build an end-to-end ITSM flow using:
    • CMDB
    • Discovery
    • Service mapping/alignment
    • Event-driven operations
  • Final deliverable: a full ITOM pipeline

Pipeline steps (example workflow)

  • Discovery infrastructure to populate CMDB
  • Perform mapping
  • Generate event data
  • Trigger incident
  • Perform tasks like:
    • Validate CMDB
    • Map business applications
    • Auto-create incident

Also mentioned

  • “Integration of all the model finally” (tying the modules together)

AI / Agent discussion (how it connects to the course)

  • Amit argues that AI demand is rising and professionals should understand how AI/agents apply to infrastructure operations.
  • AIOps inclusion (within Event Management)
    • AI Ops will be covered, but after meeting prerequisites
  • Prerequisite stance
    • For AIOps, Amit claims Python knowledge is required (not expert-level, but some programming knowledge).
    • He discourages learning JavaScript for this path.
  • Illustrative example(s)
    • Mentions integrating security AI (e.g., EntropyMitus / Entropy Cloud referenced) that scans continuously, applies data governance policies, and alerts senior personnel.
  • LLM model usage education
    • Mentions using Python libraries such as Hugging Face Transformers
    • Examples include models like GPT/T5 and tasks like classification, sentiment, chat, translation, and summarization
    • Emphasizes understanding how to use models, not deep coding mastery

GRC coverage (Governance, Risk, and Compliance)

  • When asked about GRC, Amit confirms it will be included (supporting workflow/controls).

GRC topics described

  • Risk assessment scoring:
    • Probability
    • Impact
    • Score
  • Risk management (including vendor risk management)
  • Audit management
  • Policy compliance management
  • Governance
  • “Monitor, audit, improve” workflow logic

Course logistics / requirements (as stated)

Ideal learner background

  • ServiceNow ITOM can be learned directly even without an ITSM admin course, provided the learner understands fundamentals.
  • Cloud experience (AWS/Azure) is helpful.

ServiceNow experience requirement (clarification)

  • Prior ServiceNow experience isn’t strictly mandatory for some learners, but relevant experience helps.

Class schedule

  • 9:00 PM to 10:00 PM IST
  • Monday to Friday

Duration

  • Minimum targeted: 30–35 hours (with potential extra content added)

Troubleshooting emphasis

Amit addresses concerns that troubleshooting is the “difficult part.”

  • His approach:
    • Troubleshooting improves through strong fundamentals + maximum labs + multiple scenarios
    • Practice-based learning by adding scenarios and exercises to build troubleshooting capability

Speakers / sources featured

  • Speaker: Amit
    • Solutions architect / lead engineer (IBM mentioned)

Sources/products mentioned

  • IBM (including references like “IBM Bob / IBM Bob AI”)
  • Hugging Face Transformers (Python/LLM libraries)
  • AWS and Azure
  • Nagios (as an event source example)
  • Dynatrace (mentioned in a question context)
  • CloudWatch (AWS/Azure context)
  • EntropyMitus / Entropy Cloud (security AI example)

Original video