The Relationship Conundrum
An e-commerce company has a CMDB with CIs for servers, applications, and databases. They have defined relationships between CIs, but the relationships are inconsistent: some are 'depends on', others are 'runs on', and there is no standard. When an incident occurs on a database, the support team struggles to identify which applications are affected because the relationships are not reliable. The company wants to implement service mapping to automatically discover application dependencies. However, they have a hybrid environment with both on-premises and cloud resources, and the service mapping tool they purchased only supports on-premises discovery. The team is considering manually maintaining the relationships for cloud resources.
1. What is the primary issue with the current relationship data, and how does it impact incident management?
Read the worked answer
The primary issue is the lack of a standardized relationship model. Inconsistent relationship types (e.g., 'depends on' vs 'runs on') lead to ambiguity and unreliable impact analysis. For incident management, when a database fails, the team cannot quickly determine which applications depend on it because the relationships are not consistently defined or maintained. This increases mean time to resolve (MTTR) and can lead to missed affected services.
2. Given the tool limitation for cloud resources, what approach would you recommend to ensure reliable relationships for cloud CIs? Consider CSDM and manual vs. automated methods.
Read the worked answer
Recommend using CSDM to define standard relationship types (e.g., 'Depends on::Used by') and apply them consistently. For cloud resources, since automated discovery is not available, implement a manual process with governance: assign ownership, require relationship updates during change management, and perform regular audits. Alternatively, explore cloud-native discovery tools or APIs that can integrate with the CMDB. CSDM provides a common language to integrate multiple sources. The key is to treat cloud CIs with the same rigor as on-premises, using CSDM as the blueprint.