CMDB
Common questions about the Configuration Management Database (CMDB) in ServiceOps, for IT Admins and Technicians.
What is CMDB?
A: A Configuration Management Database (CMDB) is a centralized repository used to store configuration information of IT assets and services in an organization. It is an essential part of IT Service Management (ITSM), providing a structured approach to managing IT environments.
What is the purpose of CMDB?
A: A CMDB provides a centralized database for managing and storing configuration data about IT assets and services, assisting organizations in tracking their configurations and relationships.
Is a CMDB recommended for ITIL?
A: Yes, a CMDB is highly recommended for organizations implementing ITIL as it improves the efficiency, control, and accuracy of service management in a structured manner.
What is the difference between Asset Management and CMDB?
A: The difference includes:
| Asset Management | CMDB |
|---|---|
| Asset management involves the management of physical or virtual resources owned by an organization. Examples: Hardware, Software | A Configuration Management Database (CMDB) is a centralized repository used to store configuration information of IT assets and services in an organization. |
| It focuses on financial aspects like purchasing, depreciation, and cost tracking. | It focuses on the configurations and relationships between IT components. |
| It manages individual assets. | It includes data on how assets interact and support IT services. |
| Assets, including hardware, software, and infrastructure, are valuable organizational resources that support and enable business operations. | A Configuration Item (CI) is any component within an IT environment (e.g., hardware, software, or services) that is tracked and managed through the Configuration Management Database (CMDB). |
What challenges are associated with maintaining a CMDB?
A: Common challenges include:
- Data accuracy: Keeping the information up-to-date can be difficult if changes in the IT environment are not reflected in the CMDB.
- Complexity: Managing large amounts of data, especially in complex environments, requires careful planning and consistent processes.
- Tool integration: Ensuring smooth integration with other IT systems and processes is crucial for the effective functioning of the CMDB.
Do I need a separate license for CMDB?
A: Yes. Contact your administrator or Motadata account team to get the CMDB license assigned to your account. Once assigned, the CMDB module becomes available in the portal.
What is stored in the CMDB?
A: The CMDB (Configuration Management Database) stores detailed information about Configuration Items (CIs), which can include hardware, software, systems, and services used in an organization. It tracks configurations, relationships between CIs, and their dependencies. The CMDB also records associations with: critical business services, assets, departments, users, and other related data necessary for effectively managing IT services.
What types of assets or configuration items (CIs) are stored in a CMDB?
A: A CMDB can store various types of configuration items (CIs) such as:
- Hardware (servers, routers, workstations)
- Software (applications, operating systems)
- Network components
- Virtual machines
- Documentation (policies, configurations)
- Services and dependencies between components
Who are the key users?
A: IT Administrators configure the CMDB module, define CI types, and manage discovery. Technicians create, update, and manage CIs day-to-day. Requesters and other stakeholders benefit when CIs are linked to their service requests, incidents, or changes.
What is a discovery pattern?
A: A discovery pattern is a predefined or custom set of instructions that automatically scans the network to identify, classify, and collect detailed information about both configuration items (CIs) and assets within an organization’s IT environment.
What is the difference between the classification and discovery pattern?
A: Classification pattern identifies the attributes of the device like OS or kernel. A Discovery pattern uses the results of classification and, based on the set conditions, discovers the device as a CI or asset.
Can I create an Asset from CI and vice-versa?
A: Yes, using the Sync Rule feature, you can create an Asset from a CI and vice versa.
Can I map the CI status with Asset status? How?
A: Yes. The CI Asset Status Mapping feature links the asset and CI lifecycle status. When an asset moves through its lifecycle, the CI status updates to match. For example, once an asset reaches "In Use," you can mark its CI as Operational or Non-Operational. When the asset moves to maintenance or retirement, the CI status updates accordingly.
Can a CMDB be used for cloud infrastructure?
A: Yes, ServiceOps CMDB tracks and manages both on-premise and cloud-based assets.
What are the various ways to create CI?
A: You can add a CI in multiple ways:
- Discovery: Create a CI via agent-based or agentless discovery.
- Manually: Create a CI using the Create New > Add CI option from the portal.
- Sync Rule: Create a CI automatically based on a sync rule configured on the CI type.
- Workflow: Trigger CI creation as a step in an automation workflow using the Execute Sync Rule action.
For a full walkthrough of all four methods, see Creating a CI.