ServiceNow Google Cloud Integration Guide

Architecture Overview

Implementation Steps

// Test credential configuration with a simple API call
var request = new sn_ws.RESTMessageV2();
request.setEndpoint('https://compute.googleapis.com/compute/v1/projects/' + project_id + '/zones');
request.setHttpMethod('GET');
request.setRequestHeader('Authorization', 'Bearer ' + token);
var response = request.execute();
gs.info('GCP API Response: ' + response.getBody());

// Custom discovery script for additional GCP resource types
var gcpDiscovery = new GlideRecord('discovery_definition');
gcpDiscovery.newRecord();
gcpDiscovery.name = 'GCP Production Resources';
gcpDiscovery.type = 'google_cloud_platform';
gcpDiscovery.schedule = '0 2 * * *'; // Daily at 2 AM
gcpDiscovery.credentials = credential_sys_id;
gcpDiscovery.insert();

(function process(/*RESTAPIRequest*/ request, /*RESTAPIResponse*/ response) {
    var requestBody = request.body.data;
    var pubsubMessage = JSON.parse(requestBody);
    var messageData = JSON.parse(gs.base64Decode(pubsubMessage.message.data));
    
    var incident = new GlideRecord('incident');
    incident.newRecord();
    incident.short_description = 'GCP Alert: ' + messageData.incident.incident_id;
    incident.description = messageData.incident.summary;
    incident.priority = messageData.incident.severity == 'CRITICAL' ? 1 : 3;
    incident.assignment_group = 'Cloud Operations';
    incident.u_gcp_project = messageData.incident.resource.project_id;
    var incidentId = incident.insert();
    
    response.setStatus(200);
    return { 'incident_number': incident.number.toString() };
})(request, response);

// Integration Hub Flow Action Script for GCP enrichment
var gcpAction = new sn_ih_gcp.GCPComputeActions();
var instanceDetails = gcpAction.getInstanceDetails({
    project: incident.u_gcp_project.toString(),
    zone: incident.u_gcp_zone.toString(),
    instance: incident.u_gcp_instance_name.toString(),
    connection: 'GCP_Production_Connection'
});

if (instanceDetails.success) {
    incident.work_notes = 'GCP Instance Status: ' + instanceDetails.result.status + '\n';
    incident.work_notes += 'Machine Type: ' + instanceDetails.result.machineType + '\n';
    incident.update();
}

// Validation script for CMDB GCP data quality
var gcpInstances = new GlideRecord('cmdb_ci_gcp_compute_instance');
gcpInstances.query();
gs.info('Total GCP instances discovered: ' + gcpInstances.getRowCount());

var testPubsub = {
    message: {
        data: gs.base64Encode(JSON.stringify({
            incident: {
                incident_id: 'test-123',
                summary: 'Test GCP integration incident',
                severity: 'CRITICAL'
            }
        }))
    }
};
// Send test message to webhook endpoint for validation

Common Use Cases

Troubleshooting

Pro Tips

• →Implement custom CMDB CI classes that extend the base GCP CI types to capture organization-specific attributes like cost center, environment tags, and compliance metadata from GCP resource labels. This provides richer context for incident assignment and change approval workflows while maintaining upgrade compatibility with the base GCP spoke functionality.
• →Configure Integration Hub flows with parallel processing branches for different GCP resource types to improve discovery performance and reduce overall synchronization time. Use flow logic to prioritize critical infrastructure components like load balancers and databases over less critical resources like storage buckets during discovery operations.
• →Set up custom business rules to automatically populate assignment groups and priority levels based on GCP resource labels and project metadata, enabling dynamic incident routing without manual configuration. This approach scales effectively across multiple GCP projects and environments while maintaining consistent ITSM processes.
• →Leverage ServiceNow's Event Management capabilities alongside GCP integration to correlate multiple related alerts into single incidents, reducing noise and improving operational efficiency. Configure event rules to group related GCP monitoring alerts by resource hierarchy and time windows for more effective incident management.
• →Implement custom reporting and dashboards that combine GCP billing data with ServiceNow CMDB information to provide cost visibility at the service and application level. This enables better FinOps decision-making and helps identify optimization opportunities across cloud infrastructure portfolios.
• →Use ServiceNow's orchestration capabilities to automate common GCP operational tasks like snapshot creation, instance scaling, and security group updates directly from incident and change workflows. This reduces manual effort and ensures consistent execution of standard operating procedures.

Known Limitations

• —The GCP spoke has API rate limits that align with Google Cloud quotas, typically 2000 requests per 100 seconds for Compute Engine API, which may impact large-scale discovery operations or bulk resource management tasks. Consider implementing discovery schedules during off-peak hours and using batched API calls to stay within quota limits while maintaining data freshness requirements.
• —Real-time synchronization is limited to Pub/Sub-enabled services, and some GCP resources like Cloud Storage bucket configurations or IAM policy changes may require scheduled discovery to detect modifications. Not all GCP services support comprehensive event publishing, so critical configuration changes might have delayed visibility in ServiceNow CMDB records.
• —Integration Hub Professional license is required for the GCP spoke functionality, and the number of spoke executions per month may be limited based on your ServiceNow licensing tier. Monitor spoke usage through Integration Hub analytics to avoid unexpected limitations during peak operational periods or large-scale automation scenarios.
• —Cross-region resource discovery can be complex and may require multiple discovery definitions with region-specific configurations, potentially leading to longer discovery times and increased API quota consumption. GCP global resources may not always map cleanly to ServiceNow's location-based CMDB structure without custom configuration.
• —The integration relies on service account permissions, and overly restrictive GCP IAM policies may prevent complete resource enumeration or management capabilities. Balancing security requirements with integration functionality often requires careful IAM role design and may limit some automated operational capabilities.

Frequently Asked Questions