Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Handling import failures for large GCP resources

Manage the data source failure when importing resources from GCP.

When importing large GCP resources, the data sources in the Service Graph Connector for GCP might fail because of a Direct REST response exceeding the 1024-MB limit. For more information, see REST step.

You can use one or more of the following options to handle the REST response size limitation error in the Service Graph Connector for GCP:

Save the response as an attachment

With the save response as an attachment feature, the response of each data source is temporarily stored as an attachment and after the response is read, the attachment is deleted automatically. The save response as an attachment feature is activated by default and is triggered by the sn_gcp_integ.save_rest_response_as_attachment system property.

As a user with the admin role, you can deactivate the save response as an attachment feature by setting the sn_gcp_integ.save_rest_response_as_attachment property to false. When the feature is deactivated and the response size is within the limit, the data sources run normally.

Modify the batch size

By default, the maximum batch size of the environment variable for a data source is set to 100 records. You can reduce or increase the batch size based on the data volume. To manage the batch size of a data source, you must add a system property of integer type for the data source as described in the following table.

Data sourceSystem property
SG-GCP Cloud Databasesg_gcp_cloud_db_batch_size
SG-GCP Cloud Functionsg_gcp_cloud_function_batch_size
SG-GCP Cloud Object Storagesg_gcp_object_storage_batch_size
SG-GCP Kubernetes Clustersg_gcp_kubernetes_cluster_batch_size
SG-GCP Kubernetes Cluster Rolesn_gcp_integ.sg_gcp_kubernetes_cluster_role_batch_size
SG-GCP Kubernetes Cluster Role Bindingsn_gcp_integ.sg_gcp_kubernetes_cluster_role_binding_batch_size
SG-GCP Kubernetes Deploymentsg_gcp_kubernetes_deployment_batch_size
SG-GCP Kubernetes Namespacesg_gcp_kubernetes_namespace_batch_size
SG-GCP Kubernetes Nodesg_gcp_kubernetes_node_batch_size
SG-GCP Kubernetes Podsg_gcp_kubernetes_pod_batch_size
SG-GCP Kubernetes Replicasetsg_gcp_kubernetes_replicaset_batch_size
SG-GCP Kubernetes Servicesg_gcp_kubernetes_service_batch_size
SG-GCP Load Balancersg_gcp_load_balancer_batch_size
SG-GCP Load Balancer Health Servicesg_gcp_lb_health_service_batch_size
SG-GCP Load Balancer Poolsg_gcp_lb_pool_batch_size
SG-GCP Load Balancer Pool Membersg_gcp_lb_pool_member_batch_size
SG-GCP Load Balancer Servicesn_gcp_integ.sg_gcp_lb_service_batch_size
SG-GCP Networksg_gcp_network_batch_size
SG-GCP Kubernetes Node Poolsn_gcp_integ.sg_gcp_kubernetes_node_pool_batch_size
SG-GCP Security Groupsg_gcp_security_group_batch_size
SG-GCP Software Inventorysg_gcp_software_inventory_batch_size
SG-GCP Storage Volumesg_gcp_storage_volume_batch_size
SG-GCP Storage Volume Snapshotsg_gcp_storage_vol_snapshot_batch_size
SG-GCP Subnetsg_gcp_subnet_batch_size
SG-GCP VM Instancesg_gcp_vm_instance_batch_size

Note: You must add these system properties as they aren't available by default. You must have the admin role to add or modify a system property. For more information, see Add a system property.