Posted by: Michael Disabato
I have been asked by several firms what should go into the CMDB. The answer is simple: everything.
For example, a server will need:
- The hardware
- The operating system
- Any database software running
- Any applications running
- Any patches applied (yes, they are CIs)
- Location information
- Administrator names
- Access control lists
Why all this? Because you can’t manage what you don’t know about. The CMDB stores all the CIs in the enterprise, and the linkages/dependencies between these CIs form the service chain for each delivered service. In many discussions I have focused on the technical infrastructure (servers, switches, routers, WAN, etc.), but reality demands you add the people, processes, and places as well. This not only shows you who is impacted when a failure occurs, it is necessary for good risk assessment during the Change Management process.
As Ludwig Mies van deer Rohe once said, “God is in the details.” All the details belong in the CMDB, no matter how insignificant they might be.