This is something most people will not encounter, vCOPs has a default limit of 10,000 resources it manages and reports on. If you go over this limit you will get an alert saying “Number of Resources Exceeds Supported Limit”
At one of the clients I manage has quiet a large environment with about 6000 Resources, these include VM’s, Datastores, Hosts Templates etc. So how were they over the 10,000 limit.
The client I was looking at had over 10,000 VM’s in not existing. This is because vCOPs was monitoring a sandpit self provisioning environment, so allot of machines are created then deleted. By default vCOPS does not delete these items.
There is 2 ways to fix this issue, either expand the resource limit or delete the NotExisting entries, or both if you want
Expand the Limit: add the parameter “maxNumberOfResourcesSupported=” in “/usr/lib/vmware-vcops/user/conf/analytics/advanced.properties” file. Once done restart the analytic service.
Delete Entries: Open the file “/usr/lib/vmware-vcops/user/conf/controller/controller.properties” search for “deleteNotExisiting” and change from false to true.
Then look for delerionPeriodInHours, Change this to how long you want items to remain in the not existing state before it is deleted. I usually set this to a week.
Then look for deleteionScheduledPeriod, set this to 1 hour.
Then restart the analytic service.