Interpreting Graph Layouts

Last Updated: January 7, 2026 Estimated Reading Time: 8 minutes

Overview

cmdbx offers 7 intelligent graph layouts to visualize your CMDB from different perspectives. This guide teaches you how to read each layout, understand visual cues, and extract actionable insights from your infrastructure graphs.

Graph Visualization Basics

Understanding Nodes and Edges

Nodes (circles/rectangles):

• Each node represents a Configuration Item (CI)
• Node size indicates importance/number of relationships
• Node color indicates CI type, health status, or criticality

Edges (lines/arrows):

• Connections between CIs showing relationships
• Arrow direction shows dependency flow
• Line thickness indicates relationship strength
• Line style (solid/dashed) indicates relationship type

Visual Indicators

Node Colors (default mode):

• Purple: Business Services
• Blue: Application Services
• Green: Servers/Infrastructure
• Orange: Network Devices
• Yellow: Databases
• Gray: Other/Unknown

Health Mode Colors:

• Dark Green (90-100): Excellent health
• Light Green (75-89): Good health
• Yellow (50-74): Fair health
• Orange (25-49): Poor health
• Red (0-24): Critical health

Node Shapes:

• Circle: Standard CI
• Square: Service CI
• Diamond: Network device
• Hexagon: Database/storage

Layout Types Explained

1. Force-Directed Layout

Best For: Discovering natural clusters and communities in your CMDB

How It Works:

• Nodes repel each other like magnets
• Edges pull connected nodes together
• System settles into natural groupings
• Similar/connected CIs cluster together

What to Look For:

Tight Clusters: Indicate closely related CIs

• Example: Web servers clustered with load balancers
• Insight: These CIs likely support the same service

Isolated Nodes: CIs far from others

• Example: Single server with no connections
• Insight: Possible orphaned CI or missing relationships

Bridge Nodes: CIs connecting multiple clusters

• Example: Shared database between multiple applications
• Insight: Single point of failure, critical for multiple services

Long Edges: Distant connections

• Example: Application depends on remote data center service
• Insight: Cross-region dependency, potential latency issues

When to Use:

• Initial CMDB exploration
• Finding unexpected relationships
• Identifying service boundaries
• Discovering redundant infrastructure

2. Hierarchical Layout

Best For: Understanding top-down service dependencies

How It Works:

• Top layer: Business Services (what users see)
• Middle layers: Application & Technical Services
• Bottom layer: Infrastructure components
• Dependencies flow top to bottom

What to Look For:

Pyramid Shape: Healthy service structure

• Few business services at top
• Multiple supporting services in middle
• Broad infrastructure base
• Insight: Well-distributed architecture

Inverted Pyramid: Potential problem

• Many business services
• Few supporting services
• Insight: Services may be poorly modeled or share too much infrastructure

Long Vertical Chains: Deep dependency trees

• Example: Business Service → App → Service Layer → DB → Server → Storage
• Insight: Complex dependency chain, higher risk of cascading failures

Horizontal Spread: Services at same level

• Example: Multiple application services supporting one business service
• Insight: Microservices architecture or well-decomposed service

Orphaned Top Nodes: Business services with no infrastructure

• Insight: Incomplete CMDB or misconfigured services

When to Use:

• Service impact analysis
• Understanding business-to-technical mapping
• CSDM compliance validation
• Executive reporting

3. Layer-Based Layout

Best For: Visualizing infrastructure stack (network → compute → application)

How It Works:

• Layers organized by infrastructure tier
• Bottom: Network/connectivity
• Middle: Compute/storage
• Top: Applications/services
• Horizontal grouping by function

What to Look For:

Stacked Layers: Clear separation of concerns

• Network layer complete
• Compute layer built on network
• Applications built on compute
• Insight: Well-architected infrastructure

Gaps in Layers: Missing tier

• Example: Applications directly on network without compute
• Insight: CMDB relationship gaps

Cross-Layer Connections: Direct connections skipping layers

• Example: Application directly to network device
• Insight: Non-standard architecture or CSDM violation

Layer Thickness: Number of CIs per layer

• Thick compute layer: Infrastructure-heavy
• Thick application layer: Service-heavy
• Insight: Infrastructure investment patterns

When to Use:

• Infrastructure planning
• Technology stack analysis
• Dependency validation
• Datacenter modeling

4. Business Service Layout

Best For: Grouping infrastructure by business service ownership

How It Works:

• CIs grouped by business service they support
• Each cluster represents one business service
• Size indicates service complexity
• Connections show inter-service dependencies

What to Look For:

Service Boundaries: Clear separation between services

• Minimal cross-service connections
• Insight: Good service isolation, easy to manage independently

Tangled Connections: Many cross-service dependencies

• Insight: Monolithic architecture, difficult to change independently

Service Size: Number of CIs in each cluster

• Large clusters: Complex services
• Small clusters: Simple services
• Insight: Where to focus simplification efforts

Shared Components: CIs connected to multiple services

• Example: Shared database or authentication service
• Insight: Critical dependencies affecting multiple services

When to Use:

• Service ownership mapping
• Business impact analysis
• Service rationalization
• Cost allocation

5. Network Topology Layout

Best For: Understanding network connectivity and zones

How It Works:

• Organizes by network zones/segments
• Groups by IP address ranges or VLANs
• Shows physical/logical network structure
• Highlights network devices and connections

What to Look For:

Network Zones: Distinct regions

• DMZ, Internal, Datacenter, Cloud
• Insight: Security boundaries and segmentation

Zone Bridges: Connections between zones

• Firewalls, routers, VPN gateways
• Insight: Critical security and routing points

Dense Subnets: Many CIs in one network zone

• Insight: Potential broadcast domain issues or IP exhaustion

Isolated Networks: Zones with no external connections

• Insight: Air-gapped networks or missing connection data

When to Use:

• Network planning
• Security analysis
• Troubleshooting connectivity
• Disaster recovery planning

6. CSDM Stack Layout

Best For: Validating CSDM compliance visually

How It Works:

• Enforces CSDM 4-layer model
• Layer 1: Business Services
• Layer 2: Application Services
• Layer 3: Technical Services
• Layer 4: Infrastructure Components
• Only valid CSDM relationships shown

What to Look For:

Proper Stacking: Each layer feeds the layer above

• Insight: CSDM compliant service model

Missing Layers: Gaps in the stack

• Example: Business Service directly on Infrastructure (skips Layer 2)
• Insight: CSDM violation, needs Application Service layer

Red Connections: Invalid CSDM relationships

• Insight: Relationships violating CSDM rules

Orphaned Services: Services not connected through CSDM hierarchy

• Insight: Services not properly modeled

When to Use:

• CSDM compliance audits
• Service modeling validation
• Training on CSDM principles
• Before submitting to ServiceNow certification

7. Grid Layout

Best For: Organized browsing of large CMDBs

How It Works:

• CIs arranged in a grid pattern
• Organized by CI type in rows/columns
• Relationships shown as connecting lines
• Alphabetical or custom sorting

What to Look For:

CI Distribution: How many of each type

• Many servers, few applications: Infrastructure-heavy
• Many applications, few servers: Virtualized/cloud
• Insight: Technology adoption patterns

Connection Density: How connected CIs are

• Highly connected: Critical shared services
• Sparsely connected: Independent systems
• Insight: Coupling and dependency levels

Organized Sections: Clean groupings

• All web servers together
• All databases together
• Insight: Consistent naming and classification

When to Use:

• Browsing large CMDBs systematically
• CI inventory verification
• Comparing similar CI types
• Creating documentation screenshots

Advanced Graph Reading Techniques

Pattern Recognition

Star Pattern: One central node with many connections

• Central node is critical shared service
• Example: Authentication service used by all apps
• Risk: Single point of failure

Chain Pattern: Linear dependencies

• A → B → C → D
• Example: Frontend → API → Service → Database
• Risk: Long chain means cascading failures propagate

Mesh Pattern: Many interconnected nodes

• Indicates complex interdependencies
• Example: Microservices with many service-to-service calls
• Risk: Difficult to change, high blast radius

Island Pattern: Disconnected clusters

• Separate services with no shared infrastructure
• Good: Can be managed independently
• Bad: May indicate CMDB gaps if they should be connected

Using Filters Effectively

Filter by Health:

1. Show only CIs with health < 50%
2. Identify if they cluster (systemic issue) or spread (individual issues)
3. Clustered poor health = underlying infrastructure problem

Filter by Criticality:

1. Show only Critical CIs
2. Check if they have redundancy (duplicated in graph)
3. Single critical CIs = high-risk points

Filter by Environment:

1. Show Production only
2. Verify all production CIs have owners and proper relationships
3. Compare to Dev/Test for consistency

Filter by CI Type:

1. Show only Servers
2. Check which have applications (should have connections upward)
3. Servers with no upward connections may be abandoned

Combining Layouts for Deep Analysis

Workflow Example: Understanding Service Dependencies

1. Start with Business Service Layout

   • Identify target business service cluster
   • Note which other services it connects to

2. Switch to Hierarchical Layout

   • See full dependency chain from business to infrastructure
   • Identify critical path

3. Switch to CSDM Stack

   • Validate service structure is CSDM compliant
   • Note any violations

4. Switch to Force-Directed

   • Check for unexpected connections
   • Find hidden dependencies

5. Run Blast Radius

   • Simulate failure and see actual impact
   • Compare to what graph layouts suggested

Practical Use Cases

Use Case 1: Planning a Server Decommission

1. Open Dependency Map, search for target server
2. Use Hierarchical Layout to see what depends on the server
3. Switch to Business Service Layout to identify affected services
4. Run Blast Radius to confirm impact
5. If impact is unacceptable, find alternative hosting in graph

Use Case 2: Optimizing Infrastructure Costs

1. Use Grid Layout to browse all servers
2. Filter by Environment: Production
3. Color by Criticality
4. Identify low-criticality servers with many resources
5. Check dependencies in Force-Directed layout
6. Consolidate or downsize low-criticality, low-dependency servers

Use Case 3: Improving CSDM Compliance

1. Use CSDM Stack Layout
2. Filter to show only violations (red connections)
3. Note most common violation type
4. Switch to CSDM Workbench
5. Fix violations using visual modeling
6. Return to CSDM Stack to verify fixes

Use Case 4: Incident Response

1. When service outage occurs, open Dependency Map
2. Search for affected CI
3. Use Hierarchical Layout to trace up to business service
4. Use Force-Directed to find alternative paths
5. Identify workaround by routing around failed CI

Best Practices

1. Start Broad, Narrow Down: Begin with Force-Directed, then switch to specialized layouts
2. Use Multiple Layouts: Each layout reveals different insights
3. Filter Before Visualizing: Large graphs (10,000+ nodes) need filtering
4. Save Custom Views: Bookmark useful filter + layout combinations
5. Export for Documentation: Save screenshots for runbooks and change requests
6. Update CMDB First: Graphs are only as accurate as your data
7. Learn Patterns: Recognize healthy vs. unhealthy graph patterns

Related Articles

• Dependency Map - Using the graph explorer
• Blast Radius - Impact analysis
• CSDM Workbench - Visual service modeling
• Health Dashboard - Monitoring CMDB health

Need Help?

Contact [email protected] or use the AI Assistant to ask questions about your specific graph patterns.