Skip to main content

Business Service Analyzer User Guide

Getting Started

Prerequisites

  • Network discovery must be running and collecting data
  • Software catalog should be populated
  • User must have appropriate permissions

Accessing the Feature

  1. Navigate to CMDBBusiness Service Analyzer
  2. Click "Analyze New Service" to start

Step-by-Step Guide

Step 1: Service Description

  1. Service Name: Enter a descriptive name (e.g., "Email Service", "SAP ERP")
  2. Description: Provide detailed description of the service's purpose
  3. Category: Select from predefined categories:
    • ERP
    • Email
    • Database
    • Web Application
    • Authentication
    • Monitoring
    • Custom

Tips:

  • Be specific in your description
  • Include key business functions
  • Mention critical components if known

Step 2: Software Selection

  1. Search Software Catalog: Type to search for relevant software
  2. Select Multiple Items: Choose all software related to your service
  3. Manual Entry: Add software not in catalog if needed

Example for Email Service:

  • Microsoft Exchange Server
  • Exchange Management Tools
  • IIS Web Server
  • .NET Framework

Step 3: AI Enrichment

The system automatically:

  1. Analyzes your selections
  2. Suggests additional:
    • Related processes
    • Network ports
    • Search patterns
    • Connected software

Review and Modify:

  • ✓ Accept suggested items
  • ✗ Remove irrelevant suggestions
    • Add manual entries

Step 4: Discovery Configuration

Configure discovery parameters:

  1. Time Range: Select data collection period

    • Last 24 hours (recent activity)
    • Last 7 days (typical week)
    • Last 30 days (comprehensive)
  2. Discovery Scope: Review what will be searched

    • Process names
    • Software patterns
    • Port ranges
    • Network patterns
  3. Start Discovery: Click to begin automated discovery

Step 5: Discovery Preview

Review discovered components:

  1. Servers Tab:

    • View all discovered servers
    • See running processes
    • Check confidence scores
    • Select/deselect servers
  2. Connections Tab:

    • Network connections between servers
    • Communication patterns
    • Port usage
    • Connection frequency
  3. Refinement Options:

    • Remove false positives
    • Add missed servers manually
    • Adjust classification if needed

Step 6: Results & Analysis

Explore comprehensive results:

  1. Servers View:

    • Organized by tier (Frontend, Application, Data, Infrastructure)
    • Role classification with confidence
    • Key processes per server
    • Operating system details
  2. Insights Tab:

    • Executive summary
    • Business impact analysis
    • Technical architecture
    • Identified risks
    • Recommendations
  3. Visualization:

    • Interactive service map
    • Dependency visualization
    • Communication flows
    • Tier-based layout
  4. Save Options:

    • Save as Business Service CI
    • Export documentation
    • Schedule periodic re-discovery

Understanding Results

Server Classification

Roles:

  • web-server: Front-end web servers
  • app-server: Application servers
  • database: Database servers
  • message-broker: Messaging systems
  • load-balancer: Load balancers
  • cache-server: Caching systems

Confidence Scores:

  • 🟢 90-100%: High confidence
  • 🟡 70-89%: Medium confidence
  • 🔴 Below 70%: Low confidence

Service Tiers

  1. Frontend: User-facing components
  2. Application: Business logic layer
  3. Data: Databases and storage
  4. Infrastructure: Supporting services

AI Insights

Business Impact:

  • Criticality: Critical/High/Medium/Low
  • Affected users estimate
  • Downstream dependencies

Technical Analysis:

  • Architecture pattern
  • Redundancy assessment
  • Scalability evaluation
  • Performance considerations

Best Practices

Before Starting

  1. Ensure recent discovery data (< 7 days old)
  2. Update software catalog if needed
  3. Gather service documentation
  4. Know key application names

During Analysis

  1. Start with well-known software
  2. Review AI suggestions carefully
  3. Use appropriate time ranges
  4. Validate discovered servers

After Analysis

  1. Save service immediately
  2. Review periodically (monthly)
  3. Update after major changes
  4. Share with team members

Troubleshooting

No Servers Found

  • Check discovery data age
  • Verify process names
  • Expand time range
  • Check tenant/scope settings

Missing Servers

  • Manual process entry
  • Check network segmentation
  • Verify discovery agent coverage
  • Review firewall rules

Incorrect Classification

  • Adjust manually in preview
  • Provide more specific description
  • Check for multiple roles on server

Performance Issues

  • Reduce time range
  • Limit process patterns
  • Break complex services into components

Advanced Features

Manual Overrides

  • Edit server roles
  • Adjust tier assignments
  • Modify confidence scores
  • Add custom metadata

Integration Points

  • Links to server CIs
  • Creates relationships
  • Updates AI insights
  • Triggers notifications

Automation

  • API endpoints available
  • Scheduled re-discovery
  • Alert on changes
  • Report generation

Security Considerations

  • Data remains tenant-isolated
  • No credentials stored
  • AI processing uses anonymized data
  • Audit trail maintained