Record removal process in Service Graph Connector for GCP

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Record Removal Process in Service Graph Connector for GCP

    The Service Graph Connector for GCP manages record removal through soft and hard deletion methods. This process updates the Install Status field of associated CMDB CI classes to reflect any retired or deleted records when resources are discovered and later deleted.

    Show full answer Show less

    Key Features

    • Soft Deletion: Records are marked as retired rather than permanently deleted, allowing for future reference or restoration. This feature is implemented from version 1.11.0, which checks the Last Scan attribute in the Source [sysobjectsource] table to identify undiscovered CIs.
    • Hard Deletion: This method permanently removes records from the system. The SG-GCP Software Inventory data source employs hard deletion for its records.
    • Connection Properties: Key properties include Use Record Removal, which is set to true post-upgrade, and lookbacktimeindays, which defaults to null and typically is set to 15 days after the initial run.
    • Data Sources: Soft deletion is enabled for various GCP data sources, including Kubernetes resources, storage volumes, and more.

    Key Outcomes

    By utilizing the Service Graph Connector for GCP's record removal process, customers can ensure that their CMDB remains up-to-date, reflecting accurate status for configuration items. Soft deletion allows for better data management by retaining records for potential future use, while hard deletion provides a clean slate for obsolete data.

    The Service Graph Connector for GCP uses soft deletion and hard deletion to manage the removal of records.

    Record removal is the process of handling data that is no longer needed. For any discovered resources that are deleted later after pulling data, the Service Graph Connector for GCP automatically updates the Install Status field of the associated CMDB CI classes to indicate any retired or deleted records.

    Soft deletion

    Soft deletion involves marking the install status of a record as retired rather than permanently deleting it from the system. The record remains in the database, making it possible to reference or restore it later.

    Integration Commons Record Removal is implemented from Service Graph Connector for GCP version 1.11.0 to mark the Install Status and Operational Status of configuration items (CIs) as retired if they aren't discovered during the latest pull​. This implementation verifies the Last Scan attribute of the CIs in the Source [sys_object_source] table to identify CIs that aren't discovered during the latest pull​. Additionally, the source native keys (SNKs) for all CIs are modified to include the connection alias ID to identify the connection that discovered specific CIs.

    Soft deletion for the Service Graph Connector for GCP 1.11.0 version relies on the Source [sys_object_source] table and the Use Record Removal and lookback_time_in_days connection properties. Soft deletion for the Service Graph Connector for GCP 1.10 version and earlier relied on the SG-GCP Extension Attributes [sn_gcp_integ_extension_attributes] table.

    After upgrading to version 1.11.0, the value of the Use Record Removal connection property is set to true when the import is run for the first time. Consequently, the latest SNKs for the CIs are included in the Source [sys_object_source] table. Record removal is implemented from the subsequent run.

    After upgrading to version 1.11.0, the value of the lookback_time_in_days connection property is set to null by default. During the initial run after the upgrade, the Source [sys_object_source] table is queried for all records that the connection discovered. By default, the value is set to 15 after the initial run. Two weeks after the initial run, the Source [sys_object_source] table is queried for all records that weren't discovered in the past 15 days. All records that weren't discovered in the past 15 days are marked as retired.

    Soft deletion is enabled for the following data sources in Service Graph Connector for GCP:
    • SG-GCP Folder
    • SG-GCP Project
    • SG-GCP Network
    • SG-GCP Subnet
    • SG-GCP Storage Volume
    • SG-GCP Storage Volume Snapshot
    • SG-GCP Security Group
    • SG-GCP VM Instance
    • SG-GCP Load Balancer Pool
    • SG-GCP Load Balancer Pool Member
    • SG-GCP Load Balancer Health Service
    • SG-GCP Load Balancer
    • SG-GCP Load Balancer Service
    • SG-GCP Cloud Database
    • SG-GCP Cloud Function
    • SG-GCP Cloud Object Storage
    • SG-GCP Kubernetes Cluster
    • SG-GCP Kubernetes Node
    • SG-GCP Kubernetes Pod
    • SG-GCP Kubernetes Service
    • SG-GCP Kubernetes Namespace
    • SG-GCP Kubernetes Deployment
    • SG-GCP Kubernetes Replicaset
    • SG-GCP Kubernetes Cluster Roles
    • SG-GCP Kubernetes Cluster Role Binding
    • SG-GCP Kubernetes Node Pool

    From Service Graph Connector for GCP version 1.10.0, the SG-GCP Generic Resource data source uses the post-script method for soft deletion, which relies on the Source [sys_object_source] table. For more information about the post-script method, see Post-script method.

    Hard deletion

    Hard deletion involves permanently deleting a record from the system. The record is removed from the CMDB and can't be referenced or restored later. The SG-GCP Software Inventory data source uses the hard deletion method for the deletion of records.