Skip to main content

CMDB Overview

A Configuration Management Database (CMDB) stores information about every significant component in your IT environment. It goes beyond a simple asset list by tracking the relationships between components, so you can see how technology supports your business services. When something breaks or changes, those relationships tell you exactly what else is affected.

Key Concepts of CMDB​

  • Configuration Items (CIs): A CI is any component that needs to be managed to deliver an IT service. This isn't just hardware; it includes software, documentation, locations, and even users. Each CI is a unique record in the CMDB, containing attributes that describe its characteristics.
  • CI Relationships: These are the connections that link CIs together, defining their interdependencies. Understanding that a web server is hosted on a physical server which runs an operating system is crucial for impact analysis and root cause identification.
  • Service Mapping: This is the practice of linking CIs to the business services they support. It creates a top-down view, allowing you to visualize how a technical component failure could impact a critical business function like "Online Checkout."

Examples of Common CIs​

Type: Physical Server

  • Hostname: PROD-WEB-01
  • IP Address: 10.0.1.15
  • Status: In Production
  • Owner: IT Infrastructure Team
  • Location: Data Center A, Rack 2, Unit 5
  • Model: Dell PowerEdge R740
  • Warranty Expiry: 2027-08-20

Key Capabilities & Benefits​

Core Features
  • Centralized Repository: A single, reliable source of information for all IT components and their relationships.
  • Automated Discovery: Automatically discover and populate the CMDB with CIs from your IT environment using agent-based or agentless methods.
  • Relationship & Dependency Mapping: Define and visualize the complex relationships between CIs, creating a comprehensive map of your IT ecosystem.
  • Impact Analysis: Simulate the impact of a change or failure on a CI to see all the other CIs and business services that would be affected.
  • Lifecycle Tracking: Manage the entire lifecycle of a CI, from its creation and deployment to its retirement.
Business Benefits
  • Enhanced Visibility & Control: Gain a complete and accurate picture of your IT environment, enabling better decision-making.
  • Faster Incident Resolution: By understanding CI relationships, support teams can quickly identify the root cause of an incident and its downstream impacts.
  • Reduced Risk for Changes: Perform robust impact analysis before deploying a change to understand potential conflicts and minimize the risk of service disruptions.
  • Improved Compliance: Maintain a detailed, auditable record of your IT infrastructure and its configuration to meet regulatory and policy requirements.
  • Strategic Alignment: Clearly link IT infrastructure to the business services it supports, helping to align IT activities with business goals.
Common Use Cases
  • Change Impact Analysis: Before approving a change, use the CMDB to see what services and other CIs will be affected.
  • Incident Root Cause Analysis: When a service fails, trace its dependencies in the CMDB to quickly pinpoint the failing component.
  • Asset Management Integration: While ITAM tracks the financial and contractual details of assets, the CMDB tracks their operational relationships and impact on services.
  • Security & Compliance Audits: Provide auditors with a complete map of your IT environment and its configurations.

Getting Started with Your CMDB​

Follow these steps to set up your CMDB and create your first CI in ServiceOps.

  1. Confirm you have the CMDB Specialist Technician role and a CMDB license. Contact your administrator if either is missing.
  2. Set up your CI types and statuses in Admin. See CI Type Configuration and CI Status Configuration.
  3. Create your first CI using discovery, manual entry, sync rules, or workflows. See Creating a CI.
  4. Map CI status values to your asset status values. See CI Status Configuration.
  5. Link your CIs to each other to build a relationship map. See CI Relationships and Dependencies.