The vCenter Database utilizes most of the available CPU, impacting vCenter Server performance. Stopping nworks Collectors brings the CPU usage back to normal. The nworks vmspi log shows the following errors:
VCEVT+** [VC250] retrieveEvents: createFilter failed, System.Net.WebException: The operation has timed out
nworks can use a vCenter-side event filter to reduce the traffic back to the Collector. The filtering, however, turns out to impact vCenter Database performance.
In nworks Web UI, go to the Enterprise Manager tab, select the Collector in the hierarchy on the left and click Advanced settings.
Find the EnableVcVerboseFilter setting and set it to False.
You will be prompted to restart the Collector. To do that, select the Collector and click the Restart button.
Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.