We are running SG-AWS and SG-Azure(without SSM deep discovery) to discovers all standard cloud resources since July 2025. Our priority for public cloud resource focused on the Virtual Machine Instance resource created in the cmdb_ci_vm_instance table. (where all the compute resources are stored)
Recently we were brought to attention that there are a lot Virtual Machine Instance CI (50k+ stale CI since we last setup the SGC) discovered by SG-AWS and SG-Azure appears to be stale/outdated (most recent discovery date >3 months)
We also noticed that majority of these stale CIs has the same "first discovered date" and "most recent discovery date". (indicates that it was created when it first discovered but never get discovered again on the next day)
We also setup the connector in another lower instance and these stale CIs are no longer discovered by SGC.
When we enquire our cloud administrator, we realized that all these stale CIs no longer exist in cloud.
I do noticed that SGC data source send the isDeletedResource=true update to retire/terminate the CIs. However they doesn't seem to be consistently doing this for all Virtual Machine Instance CI.
Does anyone have any insight on how SGC handle the CI lifecycle state? Or what is the standard practice on handling CI lifecycle status from Service Graph Connector?
