Skip to main content

Infrastructure Analysis

Infrastructure Analysis is the recommended starting point for mapping your environment. It automatically scans your entire infrastructure against all available service patterns to discover and classify business services without requiring manual pattern selection.

How It Works​

Infrastructure Analysis performs a comprehensive scan in four phases:

  1. Fetch Configuration Items: Loads all Server-type CIs from your CMDB
  2. Load Installed Software: Retrieves software inventory for pattern matching
  3. Pattern Matching: Matches CIs against all active service patterns (SAP, Exchange, CyberArk, etc.)
  4. Deep Analysis: For each matched service, performs discovery, classification, and AI insights generation

Starting Infrastructure Analysis​

Step 1: Access the Business Service Analyzer​

  1. Navigate to CMDB in the left sidebar
  2. Click on Business Service Analyzer

Business Services Dashboard

Step 2: Click "Perform Infrastructure Analysis"​

Click the blue "Perform Infrastructure Analysis" button at the top of the page.

The system will immediately begin the analysis process, showing real-time progress.

Understanding the Analysis Progress​

Infrastructure Analysis in Progress

The progress screen shows each step of the analysis:

Phase 1: Data Collection​

StepDescription
Starting infrastructure analysis...Initializing the analysis engine
Fetching server configuration items from database...Loading all Server CIs for your tenant
Found X configuration itemsTotal servers that will be analyzed
Loading installed software data...Retrieving software inventory
Found X installed applicationsSoftware packages available for pattern matching

Phase 2: Pattern Matching​

StepDescription
Identifying service patterns from infrastructure data...Matching CIs against all active patterns
Identified X service patternsNumber of services discovered

The system displays which patterns matched:

  • SolarWinds Network Monitoring Platform [Monitoring] (1 CIs)
  • Active Directory Domain Services [Security] (3 CIs)
  • Security Services [Security] (1 CIs)
  • SAP ERP System [Enterprise] (9 CIs)
  • Microsoft SQL Server Infrastructure [Database] (1 CIs)
  • And more...

Phase 3: Service Processing​

For each discovered service, the system performs:

  1. Step 1/4: Running CI and connection discovery - Finds all servers and their connections
  2. Step 2/4: Classifying CI roles and tiers - Assigns roles (web-server, database, app-server) and tiers (frontend, application, data, infrastructure)
  3. Step 3/4: Generating AI insights and recommendations - Creates business impact analysis, security concerns, and recommendations
  4. Step 4/4: Preparing and saving business service record - Saves the service to your CMDB

Analysis Results​

Once complete, the discovered services appear as cards on the Business Services dashboard:

Service Cards​

Each discovered service shows:

ElementDescription
Service NameName of the discovered service (e.g., "Veeam Backup & Replication")
Category BadgeService category (Infrastructure, Security, Enterprise, etc.)
Auto DiscoveredIndicates the service was found via Infrastructure Analysis
DescriptionBrief description of the service purpose
CriticalityBusiness criticality (Critical, High, Medium, Low)
Server CountNumber of servers in the service
Connection CountNumber of network connections mapped
Last AnalyzedDate of the most recent analysis

Example Discovered Services​

From the demo environment, Infrastructure Analysis discovered:

  • Veeam Backup & Replication - Infrastructure, Critical, 1 server
  • Kubernetes Container Orchestration - Infrastructure, Critical, 1 server
  • SAP ERP System - Enterprise, 4 servers, 4 connections
  • Security Services - Security
  • Active Directory Domain Services - Security
  • Prometheus Monitoring - Monitoring

Viewing Service Details​

Click "View Details" on any service card to see:

  • Servers Tab - All discovered servers with roles and tiers
  • Connections Tab - Network relationships between servers
  • Insights Tab - AI-generated analysis, recommendations, and risks
  • Visualization Tab - Interactive topology graph

These are the same detailed views available in Pattern-Based Discovery. See Understanding Discovery Results for detailed documentation.

When to Use Infrastructure Analysis​

Use Infrastructure Analysis when:

  • You want a comprehensive view of all services in your environment
  • You're starting fresh and don't know what services exist
  • You want to validate your service catalog against actual infrastructure
  • You need to discover services across multiple categories at once

Consider Pattern-Based Discovery when:

  • You know exactly which service you want to map
  • You need to customize discovery criteria for a specific service
  • You want to focus on a single service with detailed control

Best Practices​

Before Running Analysis​

  • Ensure your discovery scans are up to date - Infrastructure Analysis relies on recent scan data
  • Verify service patterns are configured - Check CMDB > Business Service Patterns for available patterns
  • Allow sufficient time - Analysis of large environments may take 2-3 minutes

After Analysis Completes​

  • Review discovered services - Verify the services match your expectations
  • Check server classifications - Ensure roles and tiers are accurate
  • Address recommendations - Use AI insights to improve your architecture
  • Schedule regular re-analysis - Keep service maps current as infrastructure changes

Managing False Positives​

If Infrastructure Analysis discovers services that don't apply to your environment:

  1. Click the trash icon on the service card to remove it
  2. Or, disable specific patterns in CMDB > Business Service Patterns

Next Steps​

After running Infrastructure Analysis: