After upgrading to vFoglight 6.6, it is not possible to see all VMs within a particular service. In total, 13 VMs (as is listed within the vSphere Client) should be listed, however, only 7 VMs are being listed within a specific vFoglight VMware Service (Services Dashboard). All of the missing VMs are collecting data, but they are just not listed within the required Service subtree.
When navigating to a specific missing VM (missing within the custom Service) through the Data Management dashboard, the VM is missing a subtree topology object "CustomAttribute". When navigating to a VM that is listed within the custom Service, it lists the "CustomAttribute". When looking at the "Review Instances and Limits" dashboard, the 'VMWCustomAttribute! toplogy object is 100% utilized (based on the default 50,000 toplogy object limit).
Toplogy limit for 'VMWCustomAttribute' has reached its limit of 50,000.
To resolve this issue, please review the following:
As the VMWCustomAttribute topology object refers to foglight.limit.instances, these changes will impact the VMWCustomAttribute immediately. Once this is completed, the missing custom data within the custom Service should populate shortly (within the next couple of collection cycles).
