cmdb-patterns

Impact analysis in ServiceNow CMDB identifies upstream and downstream dependencies for configuration items. By mapping relationship types like Depends on::Used by, you can determine which applications and business services are affected when a critical server or CI experiences an outage.

Mapping CI relationships in ServiceNow CMDB requires defining connections between configuration items using specific relationship types such as Runs on::Runs and Depends on::Used by. This establishes the dependency hierarchy needed for accurate service mapping and downstream impact analysis.

Detecting orphan and stale CIs improves CMDB health by identifying configuration items that lack active relationships or have outdated attributes. Running targeted health check scripts removes redundant data and ensures your dependency mapping and impact analysis remain accurate.

Yes, you can automate CI creation for servers and applications using ServiceNow MCP tools. By leveraging targeted scripts, you can programmatically create configuration items with essential attributes, such as a Linux server CI with a specific name and IP address, directly within the CMDB.

Key CI tables and class hierarchies in ServiceNow CMDB structure the database by categorizing configuration items from base elements down to specific servers, applications, and services. Understanding this hierarchy is essential for proper CI creation, relationship mapping, and maintaining overall data health.

No specific dependencies are required to use the patterns and scripts provided for CMDB operations. The Skill functions independently to guide CI creation and relationship mapping, but integrates with ServiceNow MCP tools for users seeking automated configuration item management.