What is a CMDB?
Short answer: A CMDB (Configuration Management Database) is the record of configuration items (hardware, software, services, processes) and the relationships between them, so changes and incidents run against a map that matches reality.
Definition
A CMDB is not a generic file store. It is the practice of collecting, maintaining and controlling information about the components needed to deliver the service: what each item is, where it is, what it depends on, and what else breaks if it fails. Hardware, software, services and processes belong in that model when they are recorded with the relationships that matter for operations.
What it is for
When there is an incident, the question is not only “which machine”. It is which services, applications and equipment depend on it. The CMDB exists to answer that without rebuilding the map in the moment.
It also underpins change: knowing what a window will touch reduces error. A list of assets without relationships is not enough; the value is in the dependencies.
What it usually holds
Hardware: equipment, storage, network, location, identifiers and maintenance data when they exist. Software: systems, applications, versions and licences. Services: mail, files, web, who uses them and who owns them. Processes: how they relate to those assets.
You do not need every brochure field. You need the record to match what is actually deployed, on one site or several.
The usual failure: it goes stale
Many ITSM tools include a CMDB. The problem is not having one: it is that it stops matching the estate. A one-off discovery describes a moment. The environment changes.
A useful CMDB is kept current. If it has to be filled in by hand after every purchase, it will become a spreadsheet under another name.
In the Azuba model
IT Environment Visibility & Intelligence treats discovery and ITAM as capabilities. The CMDB is the kind of record those capabilities have to feed if the service process (ITSM) is going to use it.
In IT visibility, Device42 covers discovery and ITAM. How it feeds a CMDB or Freshservice is assessed in the environment.
Continue
Is a CMDB the same as ITAM?
They overlap. ITAM emphasises the asset lifecycle. A CMDB emphasises configuration and relationships. A useful inventory often needs both; they are not one product by definition.
Is creating it once enough?
No. A CMDB that is not kept current describes a moment. The value is in a record that stays aligned with what is deployed.