Skyline Engineering has disabled the VC_EVENTS endpoint on all customers’ Collectors however we are diligently working on a more comprehensive strategy that will change the frequency of the VC_EVENTS data collection to every 12 hours (instead of every 30 seconds) and/or identify customers with Datacenter specific selection mode to isolate only the affected customers disable their VC_EVENTS data collection component. The impact to customers Skyline rule execution is non-existent since we do not have rules yet that actually make use of the VC_EVENTS data that is collected however, since there could be an impact to CPU and memory usage of vCenter, we have decided to disable VC_EVENTS across the board as a precaution.
The disabling of the VC_EVENTS endpoint impacts all versions of the Skyline Collector. Therefore, whether you're running version 2.2, or the most recent version, 22.214.171.124, the VC_EVENTS endpoint will be appear disabled. Once we have resolved the issue with the VC_EVENTS endpoint, we will re-enable VC_EVENTS for all Skyline Collectors.
If you have any additional questions concerning this, or need help, please let us know via this Community. Thank you for your continued feedback, comments, and questions.