Currently, the default setting to retain a resource in the No Data Receiving state is 7 days.
However, an Operations admin might want to clean up application resources from the Operations inventory and move the resources to the Not Existing state for various use cases, such as Dashboard and Relationship updates.
VCF Operations 9.0.0 and above
Workaround to achieve the desired state needs Operations administrator to update a default property in the AppOSUCP adapter config file running the Cloud Proxy appliances, where Telegraf agents are monitored.
Modify the collection cycle threshold on the Cloud Proxy to accelerate the removal of objects that no longer exist.
SSH as the root user.cd /usr/lib/vmware-vcops/user/plugins/inbound/AppOSUCPAdapter3/conf/cp config.properties config.properties.bakvi config.properties2016 to 7:MAX_COLLECTION_CYCLE_FOR_NOT_EXISTING_STATE=7service vmware-vcops restart collectorPlease note that the changes to the config.properties file are reset on upgrade. The above change will need to be re-implemented after upgrade, as the OS and Application Monitoring adapter is refreshed on upgrade.
The MAX_COLLECTION_CYCLE_FOR_NOT_EXISTING_STATE value indicates the amount of collection cycles it takes for an object to go into the Not Existing state. The default value is 2016 collection cycles, where a collection cycle is 5 minutes.
2016 * 5 = 10080 minutes
10080 / 60 = 168 hours
168 / 24 = 7 days
The value specified in the resolution above, 7 collection cycles, equals 35 minutes. This can be adjusted as desired, but it's not recommended to make this value lower than the proposed value.