ServiceNow VMware Integration Guide

Architecture Overview

Implementation Steps

// Example Flow script step to retrieve VM performance data
(function execute(inputs, outputs) {
    var connection = inputs.connection;
    var resourceId = inputs.vm_resource_id;
    
    // Call vRealize Operations API to get VM metrics
    var vrops = new sn_vrops.vRealizeOperationsClient(connection);
    var metrics = vrops.getResourceMetrics(resourceId, {
        'statKey': ['cpu|usage_average', 'mem|usage_average'],
        'begin': inputs.start_time,
        'end': inputs.end_time
    });
    
    outputs.performance_data = metrics;
    outputs.status = 'success';
})(inputs, outputs);

// Script to validate VMware CI relationships
(function() {
    var gr = new GlideRecord('cmdb_ci_vmware_instance');
    gr.addQuery('install_status', 'Installed');
    gr.query();
    
    var validationResults = [];
    while (gr.next()) {
        var relGr = new GlideRecord('cmdb_rel_ci');
        relGr.addQuery('child', gr.sys_id);
        relGr.addQuery('type.name', 'Hosted on::Hosts');
        relGr.query();
        
        if (!relGr.hasNext()) {
            validationResults.push({
                vm_name: gr.name.toString(),
                issue: 'Missing host relationship'
            });
        }
    }
    
    gs.info('VMware CI validation results: ' + JSON.stringify(validationResults));
})();

Common Use Cases

Troubleshooting

Pro Tips

• →Implement discovery behavioral parameters to exclude test or template VMs from CMDB population by configuring discovery patterns with specific naming conventions or folder exclusions, preventing CMDB pollution while maintaining comprehensive discovery of production infrastructure. Use custom CI attributes to store VMware-specific metadata like vMotion compatibility and distributed resource scheduler settings for enhanced change management workflows.
• →Configure Event Management correlation rules to suppress duplicate alarms from VMware infrastructure and implement intelligent escalation based on alarm duration and severity patterns rather than just initial severity levels. Create custom event processing scripts that enrich VMware events with CMDB data to automatically populate affected CI relationships and service impact information.
• →Leverage ServiceNow's Discovery Reconciliation framework to create custom reconciliation rules for VMware environments that account for vMotion operations and dynamic VM placement changes. Implement scheduled reconciliation jobs that verify CI relationships after significant VMware configuration changes like cluster maintenance or datacenter migrations.
• →Use Integration Hub's subflow capabilities to create reusable VMware automation patterns that combine discovery data with vRealize Operations performance metrics for comprehensive infrastructure health monitoring. Implement error handling and retry logic in custom spokes to handle temporary vCenter API unavailability during maintenance windows.
• →Optimize discovery schedules by implementing conditional discovery triggers based on VMware vCenter events rather than purely time-based schedules, reducing unnecessary discovery load while ensuring timely CI updates. Create custom dashboard widgets that correlate VMware infrastructure health metrics with ServiceNow incident and change patterns for proactive infrastructure management.
• →Implement custom MID Server capability extensions for specialized VMware discovery requirements like NSX network discovery or vSAN storage mapping that extends beyond standard discovery patterns. Use ServiceNow's Business Rule framework to automatically trigger workflows when VMware CI attributes change, enabling automated compliance checking and change approval processes.

Known Limitations

• —VMware vCenter Server API rate limiting restricts concurrent discovery sessions to approximately 100-200 simultaneous connections, requiring careful scheduling in large environments with multiple MID Servers to prevent API throttling and discovery failures. Discovery performance degrades significantly in environments with more than 10,000 VMs per vCenter Server without proper schedule optimization.
• —Event Management connector for VMware requires manual configuration of vCenter alarm forwarding and does not automatically discover or configure alarm definitions, meaning that new alarm types must be manually mapped to ServiceNow event processing rules. Real-time event processing is limited by vCenter's alarm notification capabilities and network connectivity between vCenter and ServiceNow.
• —The vRealize Operations spoke requires Integration Hub Professional licensing and additional vRealize Operations licensing for API access, which may significantly increase total cost of ownership for comprehensive VMware monitoring integration. Historical performance data retention is limited by vRealize Operations configuration and may not align with ServiceNow's data retention policies.
• —Discovery patterns do not automatically capture VMware NSX network virtualization components or detailed vSAN storage configurations, requiring custom development or third-party solutions for comprehensive software-defined datacenter discovery. Advanced VMware features like Kubernetes integration and container discovery require separate specialized discovery patterns or manual CI management.
• —MID Server deployment requirements mean that organizations must maintain additional infrastructure components with network connectivity to VMware management interfaces, potentially creating security and compliance considerations for environments with strict network segmentation requirements. MID Server high availability configurations require additional planning and infrastructure investment for critical discovery operations.

Frequently Asked Questions