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. Soft deletion for Service Graph Connector for GCP relies on the Source [sys_object_source table], which can become inefficient with large datasets.Soft deletion for Service Graph Connector for GCP relies on the SG-GCP Extension Attributes [sn_gcp_integ_extension_attributes] table. This table is regularly purged of obsolete records, improving performance and efficiency. The process marks the install status of a record as retired, but the streamlined data structure reduces overhead, enabling quicker processing and better system performance.

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.

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.

Optimized soft deletion

Optimized soft deletion enhances the soft deletion process by using a smaller, specialized table SG-GCP Extension Attributes [sn_gcp_integ_extension_attributes]. This table is regularly purged of obsolete records, improving performance and efficiency. The process still marks the install status of a record as retired, but the streamlined data structure reduces overhead, ensuring quicker processing and better system performance.

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