Apply configuration management thinking to decide which assets need CMDB-level relationship data.
Depth decision The request is to put every technical object into the CMDB, but the team needs a rule that will survive real operations. Too little relationship data hurts incidents. Too much detail creates stale records nobody trusts. Configuration relevance Record depth follows decision impact Use CMDB depth where relationships change incident, change, continuity, security, or compliance decisions. Shortcut Everything gets the same record depth. The CMDB stays useful because it carries the relationships people actually use. Existence belongs in ITAM; relationship impact earns CMDB depth. 01 Impact 02 Stability 03 Control Assess impact business service
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in