Hi Ben, I believe the main issue is your VMware agent might have stopped collecting data or is not longer collecting data for that object. Could you try solving that issue before finding a workaround (update it manually)? Please contact our Support department, create an SR and they should be able to identify why the object is not longer updating. I hope this works Gaston.
I have a question regarding changing the last updated property on a topology object. I know how to write a groovy script to update a value on a VMW Cluster object or VMW ESX Server object and submit the change via the topology service.  I am being asked to do this because our FMS & VMWare performance agent are not currently reporting in.  The virtual center objects have a last updated date of 4 days ago and other business process are checking that data and expecting it to be with in the last 24 hours.    Are there any un-intended side effects of forcing a change to the last updated date on the VM ware objects?   Is it possible this would stop collection from reporting in data prior to the last updated date? I am concerned I will create a whole in the data reported to Foglight by changing this data. Basically forcing the FMS to ignore all data prior to the new last updated
VM Ware Topology Objects Last Updated